diff options
| author | GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> | 2023-11-15 16:56:49 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-15 16:56:49 +0100 |
| commit | 30b6667cf2579bf9fbefa5f086c2d1a7ccdd3fd0 (patch) | |
| tree | 109b23f6781c35fa63ea1eb6756f3ee8e98ed5a4 | |
| parent | 26b9363ed80e805ed21d3f4f418d8f3da7b5ed75 (diff) | |
| download | NorthstarWiki-30b6667cf2579bf9fbefa5f086c2d1a7ccdd3fd0.tar.gz NorthstarWiki-30b6667cf2579bf9fbefa5f086c2d1a7ccdd3fd0.zip | |
Remove mention of next-release branch (#255)
Remove mention of next-release branch from pull request template
`next-release` only existed while there were lots of changes still
happening to wiki as everything was new. Now that the dust has settled,
the preferred approach is to just hold of merging the change until the
release has been made.
Given our faster release cycle and fewer wiki changes this usually
doesn't incur any issues with merge conflicts caused by other changes
to wiki being merged.
| -rw-r--r-- | .github/pull_request_template.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index aa32cb5..df9f138 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,6 +1,5 @@ <!-- BEFORE OPENING A PULL REQUEST: --> Check which version of Northstar your change targets. Documentation about feature not yet released should be merged into the `next-release` branch instead -> If you're adding multiple independent changes (e.g. adding a section about modding while also fixing a typo on another page) it's generally recommended to split these changes into separate pull requests. Note that pull requests containing lots of unhelpful commit messages will generally be squashed to keep commit history clean. |