-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Self-Service Fork Request: PR Workflow #20
Conversation
🎉 All set @lelia! Here's your fork: https://github.com/wayfair-contribs/typescript-action |
🚨 Hey @lelia, looks like there was an issue processing your fork request! Please ensure you've committed a properly-formatted YAML ( |
Note that the |
Co-authored-by: Gary White Jr. <7660110+GaryPWhite@users.noreply.github.com>
🎉 All set @lelia! Here's your fork: https://github.com/wayfair-contribs/filters |
Description
With #14 paving the path for semi-automated PR templates, this PR aims to fully productionize the POC introduced in #8 in order to make the
Fork a repository
PR template fully self-service for Wayfair developers. This PR also depends on theforkUrl
output introduced in forker v0.0.6 (via wayfair-incubator/forker#230).In order to test the functionality of this automated workflow, I created several 'dummy' request YAML files to ensure that the validation checks and other parsing logic worked correctly, hence the many PR approvals and fork creation comments you'll notice were left by
lhasa-ospo
.For reviewing purposes, it may be helpful to follow along in the markdown-rendered README for forking a repository (this is also linked to in the main README), to make sure the instructions are clear and easy to follow. If you'd like to test out the workflow yourself, I believe you may be able to do so by filing a PR against this branch (
self-service-fork-worfklow
) and following the aforementioned README instructions.Type of Change
Checklist
🚨 Not the PR template you wanted? Click the
Preview
tab above, then navigate back to the OSPO Automation PR Menu!