Contributing guidelines #58
Labels
No labels
bug
enhancement
good first issue
halted
help wanted
security
wait for upstream
wait to be tested
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: b3yond/ticketfrei#58
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Author: @b3yond Posted at: 18.10.2018 15:55
When you see this project and don't know the maintainers personally, it is hard to know where to start.
Other projects have contributing guidelines for this. A nice guide how to add them is here: https://help.github.com/articles/setting-guidelines-for-repository-contributors/
Against which branch should I make pull requests? How do I write an extension? ... I'm not sure if we have enough questions to answer to make this long, but short contribution guidelines are even better than long, and way better than none
Author: @git-sid Posted at: 19.10.2018 10:20
maybe we could use the git-flow model to organize our project. Here's a nice way of adding it to the user workflow https://github.com/petervanderdoes/gitflow-avh .
That way, new contributors can create a feature branch, develop the feature and create merge request when the feature is finished.