You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would suggest that we change the default branch back to main, as it is the case for >99% of all repositories I guess.
IMO it's also very confusing that our default branch and the PyPi version do not match. I would suggest to use main only for stable (released) versions and dev maybe as a general development branch where we merge all new features, fixes etc before they are combined into a new release, which is than merged to main and automatically published on PyPi (at least after #173 is live).
Simple 👍 or 👎 reactions are welcome 😀
The text was updated successfully, but these errors were encountered:
I think ideally you don't have a dev branch, but a main and a branch for the current development stream with an appropriate name. E.g. v1.4.4 which would become version 1.4.4. This branch is then deleted once merged with main. The next version branch is then generated from main.
I don't have the rights to do this change. Maybe @sravan953 can do it?
At this point we should also add a branch protection rule for main.
At least Require a pull request before merging and Require approvals should be enabled.
This can be done under Settings -> Branches -> Branch protection rules -> Add rule
I would suggest that we change the default branch back to
main
, as it is the case for >99% of all repositories I guess.IMO it's also very confusing that our default branch and the PyPi version do not match. I would suggest to use
main
only for stable (released) versions anddev
maybe as a general development branch where we merge all new features, fixes etc before they are combined into a new release, which is than merged tomain
and automatically published on PyPi (at least after #173 is live).Simple 👍 or 👎 reactions are welcome 😀
The text was updated successfully, but these errors were encountered: