WordPress / WordPress/Learn

Lesson: Continuous integration/Continuous delivery

Open
#1,300 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
333
Forks
127
Avg merge
1d 7h
Merged PRs (30d)
11

Description

Details

  • Topic title: Continuous integration/Continuous delivery
  • Topic description: A workshop covering the basics of CI/CD
  • Objective: Teach new developers what Continuous integration/Continuous delivery is, and how to use it
  • Content type: Workshop and/or tutorial
  • WordPress version:
  • Will you be creating this content?: Maybe

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.

  • SME assigned
  • Remove Needs Subject Matter Expert label
  • Content Category applied (Ex. PHP, Gutenberg, Block Theme)
  • Topic idea has passed vetting checks
  • Content type label applied
  • Priority set
  • Content Type Checklist applied
  • Content type
  • Audience set
  • Experience Level set
  • Product type (theme, plugin)
  • WordPress Version applied through Milestone (Ex. milestone 5.9)
  • If the Topic Idea reporter has not opted to create the content, apply Needs Content Creator label
  • Ticket moved to Ready to Create

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or implementation entry points are named. Start by reviewing the proposed CI/CD workshop objective and the repository's content-topic vetting guidance, then determine whether the topic is approved, who will create it, and what content type and audience are required before creation can begin.

Written by the indexing model from the issue text.

Assessment

Domain
devops, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.