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.

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

docs: add commits convention description in CONTRIBUTING.rst #83

Closed
wants to merge 3 commits into from

Conversation

paul1319
Copy link
Collaborator

@paul1319 paul1319 commented Nov 27, 2019

IPR 9897

This PR adds commit convention description in CONTRIBUTING.rst.

PR checklist:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

@paul1319 paul1319 marked this pull request as ready for review November 27, 2019 14:38
@paul1319 paul1319 requested a review from IlyaFaer November 27, 2019 14:38
@IlyaFaer IlyaFaer requested a review from mf2199 November 27, 2019 14:39
CONTRIBUTING.rst Outdated
Comment on lines 161 to 181
The commit message should be structured as follows::

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

The commit contains the following structural elements:

- **fix**: a commit of the type `fix` patches a bug in the codebase.
- **feat**: a commit of the type `feat` introduces a new feature to the codebase.
- **BREAKING CHANGE**: a commit that has a footer `BREAKING CHANGE:`, or
appends a `!` after the type/scope, introduces a breaking API change. A
BREAKING CHANGE can be part of commits of any type.
- types other than fix: and feat: are allowed, for example recommends `build:`,
`chore:`, `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, `docs:`
and others.
- footers other than BREAKING CHANGE: <description> may be provided and follow
a convention similar to `git trailer format`_.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not include standard description, as this will cause us to manually synchronize it's text if standard will be changed. Just title, short remark and links to the original standard text.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

CONTRIBUTING.rst Outdated
@@ -151,6 +151,37 @@ Exceptions to PEP8:
"Function-Under-Test"), which is PEP8-incompliant, but more readable.
Some also use a local variable, ``MUT`` (short for "Module-Under-Test").

*****************
Commit Convention
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit Message Convention

@paul1319 paul1319 requested a review from IlyaFaer November 28, 2019 11:10
Copy link
Collaborator

@IlyaFaer IlyaFaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, let's wait for comments from googlers on the original issue, and then we'll push it into Google APIs

Copy link
Collaborator

@mf2199 mf2199 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't see anything wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants