chore: Automatically build and release project #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tscharke
force-pushed
the
features/release-pipeline
branch
20 times, most recently
from
6ccc0ed to
10fa7d2
Compare
tscharke
force-pushed
the
features/release-pipeline
branch
from
10fa7d2 to
dcbc3e4
Compare
tscharke
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This MR automates the release and publishing process of this IntelliJ Plugin.
It is triggered if you create a Git Tag starting with a lowercase
v, followed by a semantic version or any string (e.g.,v1.0.0,v1.0.0-foo,vFooBar).Without the starting lowercase
v, the automated process (GitHub Action) will not start.The outcome of this automated procedure is a GitHub Release containing a ZIP file that includes the Git Tag in its name
(e.g.,
html-attribute-folder-1.0.0.zip,html-attribute-folder-1.0.0-foo.zip).If the entire procedure is successful, a GitHub Release will be generated.
However, if any errors occur during this process, no GitHub Release will be produced.
Publishing the Plugin to the JetBrains Marketplace
If the procedure is triggered by a Git Tag with a valid semantic version (like
v1.0.0), it will also be published to the JetBrains Marketplace.Alternatively, if you use a Git Tag with any other string or a string extension (e.g.,
v1.0.0-foo,vFooBar), it will only create a GitHub Release.@Flyrell I need your help 😃
Could you please take a look at this pipeline job and tell me if it's the correct gradle command you're using to release the plugin? I'm not familiar with it. If it's not correct, please tell me which commands you're actually using, and I'll add them.
And if you also provide the corresponding secrets, I can use them 😎
Btw. To run this pipeline job as well, you can simply add the git tag
v1.4.0to this branch (git tag v1.4.0).