-
Notifications
You must be signed in to change notification settings - Fork 34
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
docs: Fix status of OEP-63 #620
Conversation
OEP-63 was accepted and merged in openedx#484 but the status of the OEP hasn't been updated.
Thanks for the pull request, @antoviaque! What's next?Please work through the following steps to get your changes ready for engineering review: 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. 🔘 Let us know that your PR is ready for review:Who will review my changes?This repository is currently maintained by Where can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:
When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Hi @sarina , the bot suggested you might do the review - I have just noticed we hadn't updated the status of OEP-63 after merging it, when I looked it up today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally I'd recommend tagging authors and/or arbiters to make sure everyone agrees on the status change, but I'm happy to approve this.
cc @e0d as arbiter.
@antoviaque 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
OEP-63 was accepted and merged in #484 but the status of the OEP hasn't been updated.