File: release_trigger.md

package info (click to toggle)
changie 1.24.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,068 kB
  • sloc: makefile: 40; ruby: 38; javascript: 32
file content (19 lines) | stat: -rw-r--r-- 563 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Changie expects to be the first part of the release process as it modifies files
that are kept in the repository.

A method used by Changie itself is to detect changes to the root CHANGELOG file
as a trigger to begin the release process.
Below is how you can do that in a GitHub action.

```yaml
on:
  push:
    branches: [ main ] # your default branch if different
    paths: [ CHANGELOG.md ] # your changelog file if different

jobs:
  release:
   # do your releasing here
```

Then you can use Changie to update your changelog and let your action do the rest.