Skip to content

Conversation

@garrey-cyber
Copy link

⚠️ Have you followed the "contributions guideance" - https://owasp.org/www-project-web-security-testing-guide/#contributions

Content PRs should generally be made against the the project repo: "OWASP/wstg" - https://github.com/OWASP/wstg

Caution

Contributions should only be made in the proper repo against the latest content. Please don't open PRs here for versioned or stable content, they represent point-in-time state.

@github-actions
Copy link

github-actions bot commented Nov 7, 2025

⚠️ Have you followed the contributions guideance? Content PRs should generally be made against the the source repo OWASP/wstg.

@kingthorin kingthorin added the invalid This doesn't seem right label Nov 7, 2025
@kingthorin
Copy link
Collaborator

I'm not sure how we could have made it more obvious you were doing the wrong thing. It's all over the PR template and the comment bot also reminded you.

@kingthorin kingthorin closed this Nov 7, 2025
@garrey-cyber
Copy link
Author

garrey-cyber commented Nov 7, 2025 via email

@garrey-cyber
Copy link
Author

garrey-cyber commented Nov 7, 2025 via email

@kingthorin
Copy link
Collaborator

Maybe add a link or hint to those instructions instead of just a link on the published page that says "Edit on GitHub https://github.com/OWASP/www-project-web-security-testing-guide/blob/master/stable/4-Web_Application_Security_Testing/10-Business_Logic_Testing/02-Test_Ability_to_Forge_Requests.md" ? which just takes me straight to the master (which you should really call 'main') branch on the repo in context?

On Fri, Nov 7, 2025 at 10:03 AM Rick M @.***> wrote: Closed #470 <#470> . — —

Fair, sadly the edit on GitHub link is controlled by the OWASP.org theme and we can’t suppress it.

@kingthorin
Copy link
Collaborator

You might also want to change your communication style moving fwd e.g. "thanks for your contribution and support, however please next time follow the guidelines for contributing..." instead of the tone you took - thanks On Fri, Nov 7, 2025 at 10:07 AM Garrey Learmonth @.***>

Garrey, point taken. My frustration shouldn’t have been directed at you. We’ll look at how we can clarify further.

The typo issues has been fixed upstream.

@garrey-cyber
Copy link
Author

garrey-cyber commented Nov 7, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants