docs: design workflow for xblock skill tagging

[navinkarkera]

Adds document describing the whole workflow for xblock skill tagging.

Merge checklist:

• Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • make upgrade && make requirements have been run to regenerate requirements
• ./manage.py makemigrations has been run
  • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.
• Version bumped
• Changelog record added

Post merge:

• Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
    (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• PR created in course-discovery to upgrade dependencies (including taxonomy-connector)
  • This must be done after the version is visible in PyPi as make upgrade in course-discovery will look for the latest version in PyPi.

[openedx-webhooks]

Thanks for the pull request, @navinkarkera! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[navinkarkera]

@sameenfatima78 Please let me know your thoughts on the document as well as whether this is a good place to keep it.

[robrap]

1. This is immensely helpful. Thank you!
2. Were there any Rejected Alternatives to document?
3. I’ll leave the more detailed review to the teams involved.

[mphilbrick211]

Hi @moconnell1453! Flagging this for your review.

[navinkarkera]

@robrap Thank you!

Were there any Rejected Alternatives to document?

No.

[navinkarkera]

@moconnell1453 Thank you! I cannot merge it as I don't have merge rights.

[sameenfatima78]

Looks awesome @navinkarkera, thanks for this!

[sameenfatima78]

@moconnell1453 Thank you! I cannot merge it as I don't have merge rights.

@navinkarkera I'll take care of it.

[openedx-webhooks]

@navinkarkera 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.