You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Pakisan & @derberg : per @fmvilas 's suggestion in the AsyncAPI Slack, I'm formally requesting write permission for this repository so that I can create release branches -- and then issue PRs from my own fork to those release branches.
(If I'm reading the GitHub docs correctly, write permission is required to create branches.)
I'm not looking to code-review until I get more familiar with this code-base. Towards that end, please separately see my PR that makes the two of you CODEOWNERS so that you are the ones who approve of PRs.
Why do I want to create release branches?
I use this plugin heavily at the moment
Understandably, I'd rather run off of a code-reviewed release version than a self-built one
At the moment I need two release branches created so I can roll the revs and submit PRs:
one for IntelliJ IDEA 2022.2.4 -- as @Pakisan said he wanted to tackle that first before going to the 2022.3.x releases
one for IntelliJ IDEA 2022.3.1
...and who knows when IntelliJ IDEA 2023.x will drop
Please consider this request to grant me write privileges for this repo so I can take care of rev rolls -- and then all the two of you need to do is review and approve the PRs.
Thank you!
The text was updated successfully, but these errors were encountered:
@Pakisan, as I'm only helping here with logistics, it all depends on you as you contributed to this project. I know you were looking for help, we shared this "call for help" from official AsyncAPI accounts, and looks like it finally happened. Please have a look and lemme know how I can help.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Summary
The content below is basically the same as in this AsyncAPI Slack post.
@Pakisan & @derberg : per @fmvilas 's suggestion in the AsyncAPI Slack, I'm formally requesting
write
permission for this repository so that I can create release branches -- and then issue PRs from my own fork to those release branches.(If I'm reading the GitHub docs correctly,
write
permission is required to create branches.)I'm not looking to code-review until I get more familiar with this code-base. Towards that end, please separately see my PR that makes the two of you CODEOWNERS so that you are the ones who approve of PRs.
Why do I want to create release branches?
About me
In summary
Please consider this request to grant me
write
privileges for this repo so I can take care of rev rolls -- and then all the two of you need to do is review and approve the PRs.Thank you!
The text was updated successfully, but these errors were encountered: