You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Jonahss Should we revise the guidelines ? I think we should simply ask for PRs to be against master. I had originally done the incoming-pr branch so as to not break master, and have the sauce key private, but clearly that did not work.
Yeah we can just edit the docs and go to a regular PR to master system.
On Fri, Jan 8, 2016 at 8:14 AM, Parashuram N [email protected]
wrote:
@Jonahsshttps://github.com/Jonahss Should we revise the guidelines ? I
think we should simply ask for PRs to be against master. I had originally
done the incoming-pr branch so as to not break master, and have the sauce
key private, but clearly that did not work.
—
Reply to this email directly or view it on GitHub #198 (comment)
.
incoming-pr branch, cited by guidelines for contributing
i think you should take care of changin the guidelines if no more needed or rebase the incoming-pr branch to latest master.
spotted while trying to following the guidelines for opening the pull request: #197
\cc @axemclion @Jonahss
The text was updated successfully, but these errors were encountered: