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

HACKING.rst: guide people to add themselves to the CLA file #349

Merged
merged 3 commits into from
May 11, 2020

Conversation

OddBloke
Copy link
Collaborator

@OddBloke OddBloke commented May 6, 2020

This (a) gives people an easy way of getting a commit into the codebase,
and (b) saves us from having to explain this process (or do it
ourselves) for every new contributor.

HACKING.rst Outdated
@@ -57,11 +60,24 @@ Do these things once
* Read through the cloud-init `Code Review Process`_, so you understand
how your changes will end up in cloud-init's codebase.

* Submit your first cloud-init pull request, adding yourself to the
in-repository list that we use to track CLA signatures:
``tools/.github-cla-signers``
Copy link
Member

Choose a reason for hiding this comment

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

nit: could link to the actual file here and on line 71, but obviously not necessary.

OddBloke added 2 commits May 11, 2020 12:51
This (a) gives people an easy way of getting a commit into the codebase,
and (b) saves us from having to explain this process (or do it
ourselves) for every new contributor.
@TheRealFalcon
Copy link
Member

+1 to changes

@blackboxsw blackboxsw self-assigned this May 11, 2020
Copy link
Collaborator

@blackboxsw blackboxsw left a comment

Choose a reason for hiding this comment

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

Good suggestion for reducing unnecessary PRs

@blackboxsw blackboxsw merged commit f9d0414 into canonical:master May 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants