-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add a link to the github issue that will point to the generator page #3374
Comments
@ksy36 Maybe we can create a new route here. something along https://webcompat.com/outreach/33213 with either a redirection, aka Location or a Content-Location HTTP header. In case the webcompat-outreach.herokuapp.com domain is sunset or modified one day, it gives more flexibility on our side to control the redirections, instead of having users ending up with a legacy redirection going to a 4** code. |
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
ksy36
added a commit
that referenced
this issue
Nov 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Once an issue was moved to "needscontact" it would be nice to add a comment to the issue with a link to the generated outreach template, e.g. https://webcompat-outreach.herokuapp.com/issue/33213
The text was updated successfully, but these errors were encountered: