Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Naïm Favier
GHC
Commits
e5c21ca9
Commit
e5c21ca9
authored
5 years ago
by
Ben Gamari
Browse files
Options
Downloads
Patches
Plain Diff
gitlab: Mention ~"user facing" label
parent
1e52054b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/merge_request_templates/merge-request.md
+2
-0
2 additions, 0 deletions
.gitlab/merge_request_templates/merge-request.md
with
2 additions
and
0 deletions
.gitlab/merge_request_templates/merge-request.md
+
2
−
0
View file @
e5c21ca9
...
...
@@ -11,6 +11,8 @@ Please take a few moments to verify that your commits fulfill the following:
places.
*
[ ] add a
[
testcase to the
testsuite
](
https://gitlab.haskell.org/ghc/ghc/wikis/building/running-tests/adding
)
.
*
[ ] if your MR affects library interfaces (e.g. changes
`base`
) please add
the ~"user facing" label.
If you have any questions don't hesitate to open your merge request and inquire
in a comment. If your patch isn't quite done yet please do add prefix your MR
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment