Skip to content
This repository has been archived by the owner on May 4, 2022. It is now read-only.

docs(contributing): Note Conventional Commits and tips for complying #634

Merged
merged 6 commits into from
Dec 4, 2017

Conversation

apetro
Copy link
Contributor

@apetro apetro commented Dec 1, 2017

Fixes #633 .

Acknowledges in CONTRIBUTING.md that we're trying to do Conventional Commits.

Adds hints on how to locally lint commit messages and even on how to automate this.

I think the hints work in that I locally followed my own instructions to re-add this pre-commit hook. (To be fair I was only able to do this by cribbing from the PR that removed the hook ( #581 ), so, hurray for clear, discoverable change history.).

Funny anecdote: The hook caught problems with my initial commit message attempt for both all three of these commits. Writing in Sentence case with a full stop. it's an ingrained habit.


Contributor License Agreement adherence:

Include hints on locally linting commit messages.
Summarize contributor guidance now that we have >2 things to say.

You can locally lint your commit messages via a pre-commit hook by

1. Setting `"commitmsg": "commitlint -e",` in your local `package.json`
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this still needed since this is included in the package.json already?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I see. I'd inadvertently re-added this to package.json in this changeset. Hasn't meant to include that change; fixed.

You can locally lint your commit messages via a pre-commit hook by

1. Setting `"commitmsg": "commitlint -e",` in your local `package.json`
2. Having a `.git/commit-msg` script that honors the `package.json`
Copy link
Contributor

Choose a reason for hiding this comment

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

This could work, I added some notes at #535 (comment) on how this could be normalized to remove some of the manual effort.

@@ -1,5 +1,9 @@
# Contributing to `uportal-app-framework`

+ Be kind. (Uphold the Code of conduct).
Copy link
Contributor

Choose a reason for hiding this comment

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

❓ maybe include reference link to Code of conduct here?

@@ -1,5 +1,9 @@
# Contributing to `uportal-app-framework`

+ Be kind. (Uphold the Code of conduct).
+ Be an ICLA signatory. (Comply with Apereo licensing policy).
Copy link
Contributor

Choose a reason for hiding this comment

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

❓ maybe include reference link to licencing policy here?

@ChristianMurphy ChristianMurphy mentioned this pull request Dec 1, 2017
1 task
@apetro apetro force-pushed the document-commit-msg-linting branch from 15035bb to 936e25a Compare December 1, 2017 20:35
@apetro apetro merged commit f1362e4 into uPortal-Attic:master Dec 4, 2017
@apetro apetro deleted the document-commit-msg-linting branch December 4, 2017 14:42
@vertein vertein added this to the 8.0.0 milestone Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants