Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
G
Googletest
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
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
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 JiHu GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Meng
Googletest
Commits
849ed6b1
Commit
849ed6b1
authored
4 years ago
by
Mark Barolak
Browse files
Options
Downloads
Plain Diff
Merge pull request #2902 from mshingote:master
PiperOrigin-RevId: 318147761
parents
a4007e94
93dc015a
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
CONTRIBUTING.md
+1
-1
1 addition, 1 deletion
CONTRIBUTING.md
with
1 addition
and
1 deletion
CONTRIBUTING.md
+
1
−
1
View file @
849ed6b1
...
...
@@ -28,7 +28,7 @@ PR is acceptable as an alternative.
## Contributing A Patch
1.
Submit an issue describing your proposed change to the
[
issue tracker
](
https://github.com/google/googletest
)
.
[
issue tracker
](
https://github.com/google/googletest
/issues
)
.
2.
Please don't mix more than one logical change per submittal, because it
makes the history hard to follow. If you want to make a change that doesn't
have a corresponding issue in the issue tracker, please create one.
...
...
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