-
Notifications
You must be signed in to change notification settings - Fork 106
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
Lesson: Continuous integration/Continuous delivery #1300
Comments
jonathanbossenger
added
Awaiting Triage
Issues awaiting triage. See Training Team handbook for how to triage issues.
[Content] Needs SME
Content development issues requiring a Subject Matter Expert to vet the topic.
labels
Feb 2, 2023
This topic idea came out of a workshop that @Piyopiyo-Kitsune ran on WP CLI. Upfront I think the following structure would make sense
|
courtneyr-dev
added
Theme
and removed
Awaiting Triage
Issues awaiting triage. See Training Team handbook for how to triage issues.
labels
Feb 28, 2023
courtneyr-dev
changed the title
Topic Idea: Continuous integration/Continuous delivery
Tutorial: Continuous integration/Continuous delivery
Feb 28, 2023
kaitohm
moved this from 💡 Topic Ideas
to 👋 Ready to Create
in LearnWP Content - Development
Jun 1, 2023
kaitohm
removed
Plugin
[Content] Needs SME
Content development issues requiring a Subject Matter Expert to vet the topic.
labels
Jun 1, 2023
@jonathanbossenger will this be covered in a developer pathway? |
jonathanbossenger
changed the title
Tutorial: Continuous integration/Continuous delivery
Lesson: Continuous integration/Continuous delivery
Jul 8, 2024
36 tasks
It wasn't originally planned, but it's a good idea. I've added it and updated this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details
Related Resources
Links to related content on Learn, HelpHub, DevHub, GitHub Gutenberg Issues, DevNotes, etc.
Triage Checklist
Please follow this Vetting content topic ideas handbook page guide.
The text was updated successfully, but these errors were encountered: