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

Git conventions #41

Open
ifraixedes opened this issue Nov 8, 2022 · 0 comments
Open

Git conventions #41

ifraixedes opened this issue Nov 8, 2022 · 0 comments
Labels
scope:conventions Issues / PRs related to coding, style, repository, etc. conventions status:under-discussion Issues / PRs on hold for a future decision

Comments

@ifraixedes
Copy link
Collaborator

We don't have Git conventions defined in this repository and they may lead to:

  • Having discussions on the same topics over and over.
  • Having discussions of different approaches where none of them are wrong and it's a matter of personal tastes.
  • Ending up having a not neat Git commit history.

The purpose of this issue is to discuss different approaches to working with Git and reach a consensus to establish some conventions for not having the issues listed above.

At least we should agree on:

  • Git commit message conventions.
  • Git merge strategies.
  • Who is responsible to merge an approved commit / PR?
@ifraixedes ifraixedes added status:under-discussion Issues / PRs on hold for a future decision scope:conventions Issues / PRs related to coding, style, repository, etc. conventions labels Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:conventions Issues / PRs related to coding, style, repository, etc. conventions status:under-discussion Issues / PRs on hold for a future decision
Projects
None yet
Development

No branches or pull requests

1 participant