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

create policy document #4

Open
mvdweiden opened this issue Jul 15, 2021 · 2 comments
Open

create policy document #4

mvdweiden opened this issue Jul 15, 2021 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@mvdweiden
Copy link
Member

We should consider writing a policy document, which outlines how to manage this repository.

As an example: if a pull request (PR) contains only 1 commit, use a squash merge to merge it, and only then. In other case use a regular merge.
@mvdweiden mvdweiden added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 15, 2021
@mvdweiden
Copy link
Member Author

@fate4gle @GitKoenO Is this something that you guys could look at? As you probably have the most experience with github.

@fate4gle
Copy link

We could also state it the other way around, only use squash if you have a single document (and you know what you are doing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fate4gle @mvdweiden