Problem

I think our current system of merging PRs to develop then making a release to master has some flaws to it.

1. In order to use Linked Issues when merging PRs, the PRs have to be merged to the default branch aka master. By merging them into develop first, Linked Issues aren't triggered and issues aren't closed when merged.
2. Our repo relies on some Actions that need to be merged into master for it to work (workflow_run for example). By limiting PRs into master only during releases, testing the action becomes difficult because we can only test it during the next release.

Suggested feature

I think we should change our develop branch to become the default branch. This would solve the above 2 problems. The current master branch can then be changed to something like a stable-release branch or something similar.

Essentially:

1. Rename master to stable-release
2. Rename develop to master
3. Change GitHub setting to point to develop as the default branch.

Why should we have this feature?

We won't have to manually close Issues anymore. Changes that we want people to see right away when they visit the repo (README.md, CONTRIBUTING.md, GitHub Actions) would also be present after we merge.

Additional information

No response