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.

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

Decide as a cross team on branching strategies #29

Closed
derekadombek opened this issue Mar 18, 2024 · 0 comments
Closed

Decide as a cross team on branching strategies #29

derekadombek opened this issue Mar 18, 2024 · 0 comments
Assignees

Comments

@derekadombek
Copy link
Collaborator

derekadombek commented Mar 18, 2024

User Story

Currently anybody on our team is allowed to push to main. As everybody on the team starts contributing, this is going to cause conflicts. We should use PR's and block merging to main without approvals for this reason. We need to get together and discuss how we want to approve merges to main, do we want a standard mainline approach? How many approvals do PR's need, 1 or 2? Do we agree to automatically squash during merge?

Acceptance Criteria

We should at least require the use of PR's and block merges to main without approval.

@derekadombek derekadombek changed the title Decide as a team on branching strategies Decide as a cross team on branching strategies Mar 18, 2024
@derekadombek derekadombek self-assigned this Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant