docs: link to general guidelines and list recommended scopes #391
Conversation
Based on conversation here:
#389 (comment)
which was about not finding contributing guidelines for how to format
commit messages.
We could still use some more specific docs about what scopes we'd like
to see when working in the monorepo (eg. using scopes to indicate
project), so I'll put that in the next commit.
|
@kresimir-coko: in an ideal world, we'd mention the scope in every single project-specific And note that I didn't include a scope in this PR because it isn't specific to any project, and it isn't what I'd call "cross-cutting" either (ie. touching multiple projects). It's just a tiny doc tweak, and it doesn't touch any paths that would cause it to show up in project-specific changelogs, so it doesn't need a scope. |
|
@wincent Awesome! One more thing I noticed right now, in the Liferay Frontend Guidelines, the first 2 links (bolded) are pointing to a 404:
|
|
Thanks for catching the 404s! Will update. |
As pointed out here: #391 (comment)
Based on conversation here which was about not finding contributing guidelines for how to format commit messages.
We could still use some more specific docs about what scopes we'd like to see when working in the monorepo (eg. using scopes to indicate project), so I added that in the second commit.