Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change branch setup, PR goes into Main #68

Closed
Crowdedlight opened this issue Mar 3, 2024 · 2 comments
Closed

Change branch setup, PR goes into Main #68

Crowdedlight opened this issue Mar 3, 2024 · 2 comments
Assignees
@Crowdedlight
Labels
enhancement New feature or request

Comments

@Crowdedlight
Copy link
Owner

Remove develop and use PR straight to main. Helps with the tooling and documentation being up to date always, and avoid some merge conflicts.

We don't need a staging which develop was as we are releasing on tags anyway.
@Crowdedlight Crowdedlight added the enhancement New feature or request label Mar 3, 2024
@Crowdedlight Crowdedlight self-assigned this Mar 3, 2024
@Crowdedlight
Copy link
Owner Author

Waiting for #65 and Patch to be merged into develop. Then rebaseing main on develop and delete develop.

@Crowdedlight
Copy link
Owner Author

After #65 is merged, and #71, #70 is merged afterwards, we can change to rename or merge into main branch and delete "develop". And do a branch cleanup in general.
If #54 is ready, merge that before this issue, otherwise it should be fairly simple to just target "main" from that one instead of develop.

@Crowdedlight Crowdedlight mentioned this issue Mar 25, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Crowdedlight Crowdedlight

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Crowdedlight