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

branches and merging and pull requests #2

Closed
andrew-elder opened this issue Aug 1, 2018 · 5 comments
Closed

branches and merging and pull requests #2

andrew-elder opened this issue Aug 1, 2018 · 5 comments

Comments

@andrew-elder
Copy link

What is the pull request policy for this repo? ie what branch should pull requests be made to?

We should add something to the top level readme describing how to contribute to the repo.

@aguedes
Copy link
Collaborator

aguedes commented Aug 2, 2018

Since this project is in its early days, I think we should keep the PR policy as simple as possible for now. PRs should target 'master' branch. Once the PR gets Travis and code review "green light", we merge it using the option "rebase and merge", preferably.

@andrew-elder
Copy link
Author

@aguedes - pull requests to master are fine for the moment.

@andrew-elder
Copy link
Author

I'm going to close this issue.

@aguedes
Copy link
Collaborator

aguedes commented Nov 7, 2018

Hey @andrew-elder, could we please use the "rebase and merge" button when applying PRs into master branch?

The current approach creates a merge commit every time a PR is applied, resulting in a spaghetti-ish git history. The rebase-and-merge approach gives us a linear history, much easier to make sense out of it.

@andrew-elder
Copy link
Author

Yes. No problem. Previous major contributors to OpenAvnu preferred merging without rebasing, but this repo is contributed by others so I’m happy to follow their wishes.

@RioChan RioChan mentioned this issue Jan 26, 2022
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

2 participants