<NME> CONTRIBUTING.md
<BEF> 
_Wondering why something in Sagan is implemented the way that it is? Find something that doesn't work the way the [wiki](https://github.com/spring-io/sagan/wiki) says it should? Have an idea for an improvement? Want to fix or implement it yourself, even? You're in the right place!_


## Asking questions and reporting issues

Everything regarding Sagan is tracked in [GitHub Issues](https://github.com/spring-io/sagan/issues). Just create a new issue, and we'll discuss. It's a good idea to search first, though, to see if something similar has already been asked or reported.


## Pull requests

If you want to contribute code to the project, you'll need to be familiar with GitHub's notion of [pull requests] (they're awesome). See also the section below on `hub`.

We also ask that you sign our [contributor license agreement](http://support.springsource.com/spring_bsd3_committer_signup). It's not too big a deal, just a form to fill out, but it'll get even smoother soon when issue [#121](https://github.com/spring-io/sagan/issues/121) is complete.


## Coding conventions

Our formatting and import organization profiles are checked into the project under the [style](https://github.com/spring-io/sagan/tree/main/style) directory. Check out the README there for instructions how to import them into Eclipse or IDEA.


## Use `gh` for pull requests

If you're not already familiar, GitHub's [`gh`](ihttps://cli.github.com/manual/) utility that brings pull requests, issues and many other GitHub features to your terminal. It'll allow you to do super-powerful things like this:

    # nothing unusual here...
    git checkout my-feature-branch
    git push myfork my-feature-branch

    # but the following is only possible with gh--
    # it will guide you with an interactively
		# to create a PR against the upstream branch
		gh pr create


## Commit like a pro

Read Pro Git's section on [Commit Guidelines](http://www.git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Commit-Guidelines), and then read it again. Understanding how to structure git commits and properly format comments will pay off for every Git project you contribute to in the future. Look through Sagan's commit history with `git log`, and do your best to follow suit.


## Expect discussion and rework

For anything other than really trivial fixes, there will probably be some discussion involved before your pull request is merged. If you're thinking about a significant change, it's a good idea to discuss it with the team first, before spending a lot of time putting together a pull request.


## Have fun!

Thanks for your interest and participation--we'll see you over in [Issues](https://github.com/spring-io/sagan/issues)!


<MSG> Merge pull request #413 from cbeams/patch-1

Fix link to GH pull request instructions
<DFF> @@ -9,7 +9,7 @@ Everything regarding Sagan is tracked in [GitHub Issues](https://github.com/spri
 
 ## Pull requests
 
-If you want to contribute code to the project, you'll need to be familiar with GitHub's notion of [pull requests] (they're awesome). See also the section below on `hub`.
+If you want to contribute code to the project, you'll need to be familiar with GitHub's notion of [pull requests](https://help.github.com/articles/using-pull-requests) (they're awesome). See also the section below on `hub`.
 
 We also ask that you sign our [contributor license agreement](http://support.springsource.com/spring_bsd3_committer_signup). It's not too big a deal, just a form to fill out, but it'll get even smoother soon when issue [#121](https://github.com/spring-io/sagan/issues/121) is complete.
 

{'addition_count': 1, 'commit_subject': 'Merge pull request #413 from cbeams/patch-1', 'deletion_count': 1, 'file_extension': '.md', 'lang': 'md', 'license': 'bsd-3-clause', 'repo_name': 'spring-io/sagan'}