-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ConfigurationGathering.py: modify get_config_directory docstring #5882
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message should follow coala's guideline.
https://coala.io/newcomer
Also, you need to rebase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit is not following guidelines
https://coala.io/newcomer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please follow the commit guidelines given in http://api.coala.io/en/latest/Developers/Writing_Good_Commits.html
okay will do |
Changed multiple double quotes to single quotes in get_config_directory docstring Fixes coala#5858
…hriram98/coala into get_config_directory_docstring
Comment on fcf742c. Shortlog of the HEAD commit contains 119 character(s). This is 69 character(s) longer than the limit (119 > 50). Origin: GitCommitBear, Section: |
Comment on fcf742c. Shortlog of HEAD commit does not match given regex: ([^:]|[^:]+[^ ]: [A-Z0-9].*) Origin: GitCommitBear, Section: |
Comment on 3ea380a. Shortlog of the HEAD commit contains 64 character(s). This is 14 character(s) longer than the limit (64 > 50). Origin: GitCommitBear, Section: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should squash this two commits into one 👍
And I think you should take a look on travis fail and solve problems 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- You may want to
amend
the commit message as per the guidelines. - Once done, you will need to rebase it. Refer this.
- Also, read the Newcomer's Guide, if you haven't.
- Additionally, always make the CI green and happy ;)
Okay I am working on it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase before making a PR.
😉
Also, in your commit message, you need to change Fixes
to Closes
.
Read Writing good commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase all the commits into one
Squash the commits into one..
Refer to this link https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
Can be helpful
Hi, @RJ722 |
Oops, looks like I assigned over at the wrong place! |
This should be closed as #6073 has been approved |
Changed multiple double quotes to single quotes in get_config_directory docstring
Fixes #5858