Skip to content

Commit

Permalink
format
Browse files Browse the repository at this point in the history
  • Loading branch information
@zhammer
zhammer committed Jan 30, 2024
1 parent 7d3c8e6 commit 38143b1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/MAINTAINERS.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,12 @@ To actually run a release, trigger the Release workflow.
### Merging

To work with our release tooling, when merging a PR, make sure to:

- Squash into one commit
- Write a commit message that follows [conventionalcommits](https://www.conventionalcommits.org/en/v1.0.0/#summary)

See [this note](https://github.com/semantic-release/semantic-release/discussions/2275#discussioncomment-1719271) for context on why we squash rather than enforce commit message contributions from contributors.

### Future

*`multi-semantic-release` is, by the maintainers' own admission, a hack on top of [semantic-release](https://github.com/semantic-release/semantic-release), but seems to serve its purpose well now, and is used by [other Backstage plugin providers](https://github.com/janus-idp/backstage-plugins/blob/e6ba8e3c5f38381e5e1e74ebd3dac8f20567cc76/package.json#L54) (though we opt for a more up to date fork.) It does a better job than any current alternate option, and explains its advantage well [here](https://github.com/dhoulb/multi-semantic-release?tab=readme-ov-file#iteration-vs-coordination). The maintainers are migrating to their own [tool](https://github.com/semrel-extra/zx-bulk-release) which is in early dev now but is worth exploring in the future.*

_`multi-semantic-release` is, by the maintainers' own admission, a hack on top of [semantic-release](https://github.com/semantic-release/semantic-release), but seems to serve its purpose well now, and is used by [other Backstage plugin providers](https://github.com/janus-idp/backstage-plugins/blob/e6ba8e3c5f38381e5e1e74ebd3dac8f20567cc76/package.json#L54) (though we opt for a more up to date fork.) It does a better job than any current alternate option, and explains its advantage well [here](https://github.com/dhoulb/multi-semantic-release?tab=readme-ov-file#iteration-vs-coordination). The maintainers are migrating to their own [tool](https://github.com/semrel-extra/zx-bulk-release) which is in early dev now but is worth exploring in the future._

0 comments on commit 38143b1

Please sign in to comment.