That ought to be a nice, simple PR - ideal for a first timer to tackle. Any takers?
| [reply] |
a nice, simple PR - ideal for a first timer to tackle. Any takers?
Go on then hippo - I'll bite assuming you are offering to be a guide...
Not that I really have the time or capacity to take anything extra on. However, I have been wanting to use GitHub for several years. I keep reading up on it and it really doesn't make sense, so I guess the only way to understand is to jump in and this seems to be the opportunity to do that guided by the wisdom of hippo and others :)
Right now I know nothing about GitHub so expect lots of questions...
...Starting with these two or three...
- Do I need anything installed locally to use GitHub other than what I already use for development?
- Do I need to get permission/acceptance from the maintainer?
- If yes to 2 - is it best to email them or is there another protocol?
| [reply] |
Do I need anything installed locally to use GitHub other than what I already use for development?
Not necessarily. You can do it all through the GitHub web interface. However, using git on your local machine can make things easier: you can use your own choice of editor, save your work part way through, run local tests, etc.
Do I need to get permission/acceptance from the maintainer?
Not up front, no. When you make the pull request the owner of the repo will be alerted to it and will either accept it or respond with feedback prior to accepting. If you refer to the issue that has already been raised in the PR text that will help.
There is some general guidance here but essentially the process is
- Obtain a github account if you don't already have one.
- Fork the repo
- Make changes to your fork
- Raise the pull request
| [reply] |