Skip to content

[Backport] Fix redirection path if Slack webhook channel is invalid #10559

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

Conversation

jamesorlakin
Copy link
Contributor

@jamesorlakin jamesorlakin commented Mar 1, 2020

A backport of #10548 because the label was added

The path to the hook config is already defined by orgRepoCtx
@techknowlogick techknowlogick added this to the 1.11.2 milestone Mar 1, 2020
@6543
Copy link
Member

6543 commented Mar 1, 2020

@jamesorlakin you targeted the wrong branch for a backport!

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Mar 1, 2020
@lafriks lafriks changed the base branch from master to release/v1.11 March 1, 2020 19:55
@lafriks lafriks changed the base branch from release/v1.11 to master March 1, 2020 19:55
@lafriks
Copy link
Member

lafriks commented Mar 1, 2020

You need to create new commit for release/v1.11 branch

@6543
Copy link
Member

6543 commented Mar 1, 2020

git checkout -f origin/release/v1.11 -b backport_xy
git cherry-pick c08c975d368771237d6509df915d3ec315186612
git push -u origin

and select release/v.1.11 as target on pull create

(for example)

@jamesorlakin
Copy link
Contributor Author

Oh wow, whoops! I even did the cherry pick step but forgot to branch from release...

I'll be able to sort it tomorrow when I'm back home 🙂

@guillep2k
Copy link
Member

I'll close this one. 😉

@guillep2k guillep2k closed this Mar 1, 2020
@jamesorlakin
Copy link
Contributor Author

Haha, probably wise

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants