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

Add git workflow guidelines to contribute on this repo #2334

Closed
wants to merge 1 commit into from
Closed

Add git workflow guidelines to contribute on this repo #2334

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ You should fork the project into your own repo, create a topic branch
there and then make one or more pull requests back to the gravitystorm repository.
Your pull requests will then be reviewed and discussed.

A comprehensive description of this workflow, including guidelines and recommendations on how contributors should operate when collaborating to OpenStreetMap Carto through pull requests (PRs) via Git and GitHub, is provided in [GIT-WORKFLOW.md](https://github.com/gravitystorm/openstreetmap-carto/blob/master/GIT-WORKFLOW.md).

## Reporting issues

As OpenStreetMap data is always changing, rendering bug reports should **always**
Expand Down
Loading