Skip to content

Commit ddd5443

Browse files
authored
Move pull request template to Github location
Github doesn't support multiple PR templates right now, so fixing this by moving to root of .github folder.
1 parent d26209a commit ddd5443

1 file changed

Lines changed: 41 additions & 0 deletions

File tree

.github/pull_request_template.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Default
3+
about: Suggest changes to MDS
4+
title: <Insert Title>
5+
6+
---
7+
8+
# MDS Pull Request
9+
10+
Thank you for your contribution! Please review our OMF [contributing page](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md) to understand guidelines and policies for participation, and our [Code of Conduct page](https://github.com/openmobilityfoundation/governance/blob/main/CODE_OF_CONDUCT.md).
11+
12+
To avoid complications and help make the Review process as smooth as possible, make sure to:
13+
14+
1. Target [**`dev`**](https://github.com/openmobilityfoundation/mobility-data-specification/tree/dev) branch. Please ensure you are targeting **`dev`**, not **`main`**.
15+
1. Keep the *"Allow edits from maintainers"* button checked to help us resolve some issues for you.
16+
1. Be ready to resolve any merge conflicts before we approve your Pull Request.
17+
1. Have an up to date profile, per our Github [community profile](https://github.com/openmobilityfoundation/governance/blob/main/CONTRIBUTING.md#community-profile) guildance.
18+
19+
## Explain pull request
20+
21+
Please provide a clear and concise reason for this pull request and the impact of the change
22+
23+
## Is this a breaking change
24+
25+
A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).
26+
27+
* Yes, breaking
28+
* No, not breaking
29+
* I'm not sure
30+
31+
## Impacted Spec
32+
33+
Which spec(s) will this pull request impact?
34+
35+
* `agency`
36+
* `policy`
37+
* `provider`
38+
39+
## Additional context
40+
41+
Add any other context or screenshots about the feature request here.

0 commit comments

Comments
 (0)