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

#122 - Backport info about backup API call #123

Closed

Conversation

arvindsv
Copy link
Member

No description provided.

@arvindsv
Copy link
Member Author

@ketan: For #122 (review)

@ketan
Copy link
Member

ketan commented Sep 22, 2016

This will get overwritten anytime there is a commit to any of the old branches. The right way is to cherry pick #122 to each branch here https://github.com/gocd/api.go.cd/branches

@ketan ketan closed this Sep 22, 2016
@ketan
Copy link
Member

ketan commented Sep 22, 2016

No need to submit PRs to each branch. Just commit straight to the branch.

@arvindsv
Copy link
Member Author

Ah, I thought only the "current" one goes into gh-pages. Will cherry-pick.

@ketan
Copy link
Member

ketan commented Sep 22, 2016

No — all websites have a branch per release, so we can always backport
fixes, and they get applied to the documentation for the specific release.

On Thu, Sep 22, 2016 at 10:20 PM Aravind SV notifications@github.com
wrote:

Ah, I thought only the "current" one goes into gh-pages. Will cherry-pick.


You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub
#123 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAApZgrbLV7j1eVeu3eNqUQ4JSNCYKaWks5qsrHMgaJpZM4KEHTy
.

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.

2 participants