So you want to contribute to the ruby-pwsh gem: Great! Below are some instructions to get you started doing that very thing while setting expectations around code quality as well as a few tips for making the process as easy as possible.
- Fork the module repository on GitHub and clone to your workspace
- Make your changes!
- my commit is a single logical unit of work
- I have checked for unnecessary whitespace with "git diff --check"
- my commit does not include commented out code or unneeded files
- my commit includes tests for the bug I fixed or feature I added
- my commit includes appropriate documentation changes if it is introducing a new feature or changing existing functionality
- my code passes existing test suites
- the first line of my commit message includes:
- an issue number (if applicable), e.g. "(GH-xxxx) This is the first line"
- a short description (50 characters is the soft limit, excluding issue number(s))
- the body of my commit message:
- is meaningful
- uses the imperative, present tense: "change", not "changed" or "changes"
- includes motivation for the change, and contrasts its implementation with the previous behavior
- Make sure you have a GitHub account
- Create an issue, or watch the issue you are patching for.
- Push your changes to your fork
- Open a Pull Request against the repository in the puppetlabs organization
-
Make separate commits for logically separate changes.
Please break your commits down into logically consistent units which include new or changed tests relevant to the rest of the change. The goal of doing this is to make the diff easier to read for whoever is reviewing your code. In general, the easier your diff is to read, the more likely someone will be happy to review it and get it into the code base.
If you are going to refactor a piece of code, please do so as a separate commit from your feature or bug fix changes.
We also really appreciate changes that include tests to make sure the bug is not re-introduced, and that the feature is not accidentally broken.
Describe the technical detail of the change(s). If your description starts to get too long, that is a good sign that you probably need to split up your commit into more finely grained pieces.
Commits which plainly describe the things which help reviewers check the patch and future developers understand the code are much more likely to be merged in with a minimum of bike-shedding or requested changes. Ideally, the commit message would include information, and be in a form suitable for inclusion in the release notes for the version of Puppet that includes them.
Please also check that you are not introducing any trailing whitespace or other "whitespace errors". You can do this by running
git diff --checkon your changes before you commit. -
Sending your patches
To submit your changes via a GitHub pull request, we highly recommend that you have them on a topic branch, instead of directly on "main". It makes things much easier to keep track of, especially if you decide to work on another thing before your first change is merged in.
GitHub has some pretty good general documentation on using their site. They also have documentation on creating pull requests.
In general, after pushing your topic branch up to your repository on GitHub, you can switch to the branch in the GitHub UI and click "Pull Request" towards the top of the page in order to open a pull request.
-
Update the related GitHub issue.
If there is a GitHub issue associated with the change you submitted, then you should update the issue to include the location of your branch, along with any other commentary you may wish to make.
Our Puppet modules provide Gemfiles, which can tell a Ruby package manager such as bundler what Ruby packages,
or Gems, are required to build, develop, and test this software.
Please make sure you have bundler installed on your system, and then use it to install all dependencies needed for this project in the project root by running
# Unless you're doing a release, you don't need the puppet gem group
% bundle install --path .bundle/gems --without puppet
Fetching gem metadata from https://rubygems.org/........
Fetching gem metadata from https://rubygems.org/..
Using rake (10.1.0)
Using builder (3.2.2)
-- 8><-- many more --><8 --
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.NOTE: some systems may require you to run this command with sudo.
If you already have those gems installed, make sure they are up-to-date:
% bundle updateWith all dependencies in place and up-to-date, run the tests:
% bundle exec rake specThis executes all the rspec tests in the spec directory.
Even if you have commit access to the repository, you still need to go through the process above, and have someone else review and merge in your changes. The rule is that all changes must be reviewed by a project developer that did not write the code to ensure that all changes go through a code review process.
The record of someone performing the merge is the record that they performed the code review. Again, this should be someone other than the author of the topic branch.
- Slack (slack.puppet.com) #forge-modules, #puppet-dev, #windows, #voxpupuli
- IRC (freenode) #puppet-dev, #voxpupuli