Skip to content

Commit 1d14fc5

Browse files
authored
Merge pull request #68 from Deadpikle/doc/tagged-releases
Add some docs about GitHub actions and tags
2 parents 24654e5 + cb6f6d5 commit 1d14fc5

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

doc/readme.md

+14
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,20 @@ Depending on the kind of GitHub event, the run command will automatically:
167167
- If it is a `push` with a tag version (e.g `v1.9.6` as configured with `[github]` section in the configuration) it will **perform a full build with publish**
168168
- For an application, it will publish multiple cross-compiled packages to your release
169169

170+
> **NOTE about the publish process:**
171+
>
172+
> The publish process relies on a tag commit being pushed, and the GitHub action being run on that tag commit. If you have set up your GitHub action to only run on specific branches and not on tag pushes, the `dotnet-releaser` publish portion of the process will never run.
173+
To fix this and still specify specific branches to run your action on, use something like this in your GitHub action:
174+
>
175+
> ```yml
176+
> on:
177+
> push:
178+
> branches:
179+
> - main # Used for stable releases
180+
> - develop # Used for preview releases
181+
> tags:
182+
> - '*' # run on all tags being pushed
183+
> ```
170184
#### 1.2.2. Example of a GitHub CI Integration
171185
172186
An example of a setup with GitHub Actions:

0 commit comments

Comments
 (0)