Title: GitHub – Make WordPress Training

---

#  Tag Archives: GitHub

 [  ](https://profiles.wordpress.org/kaitohm/) [Kaito Hanamori](https://profiles.wordpress.org/kaitohm/)
9:08 am _on_ December 5, 2023     
Tags: GitHub, [procedures ( 35 )](https://make.wordpress.org/training/tag/procedures/)

# 󠀁[Recap: GitHub updates and process refinements](https://make.wordpress.org/training/2023/12/05/recap-github-updates-and-process-refinements/)󠁿

The [GitHub updates announced in July](https://make.wordpress.org/training/2023/07/08/next-steps-for-github-updates/)
have finally completed! Here is an overview of the changes.

## Here’s what’s new

 * GitHubGitHub GitHub is a website that offers online implementation of git repositories
   that can easily be shared, copied and modified by other developers. Public repositories
   are free to host, private repositories require a paid subscription. GitHub introduced
   the concept of the ‘pull request’ where code changes done in branches by contributors
   can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
   labels have been reduced from over 120 to just 27.
 * Issue templates have been reduced from 9 to 5.
 * 3 workflows have been set up to automate tasks:
    - Anyone can now self-assign issues by typing `//assign` in a issue comment.
    - Anyone can send their issue to the relevant project board by typing either`//
      dev`, `//content`, or `//handbook` when submitting feedback.
    - Faculty members can add content development checklists to their issues by 
      typing either `//tutorial`, `//online-workshop`, `//lesson-plan`, or `//course`
      in either the issue itself or in a comment.
 * 2 new handbook pages have been published to document these changes:
    - [GitHub Labels](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/github-labels/)
    - [Automated Workflows](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/automated-workflows/)
 * [How We Use GitHub](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/)
   and other handbook pages have been updated to reflect these changes.

## Learn more at next week’s Online Workshops

[@bsanevans](https://profiles.wordpress.org/bsanevans/) will be hosting two Online
Workshops next week to demonstrate these changes live, and answer any question folks
may have. These Online Workshops are a perfect opportunity for:

 * **Training Team Faculty and contributors** who have been contributing to the 
   team and want to get up-to-date with these latest changes.
 * **New contributors** interested in contributing to the Training Team and wanting
   to know how we use GitHub.
 * **Any contributor from other Make WordPress teams** interested in implementing
   GitHub processes to their team, too.

Come sign up to these workshops from the links below. Times are shown in your local
timezone. A recording will be published after the event for anyone who could not
attend.

 * [Session 1 sign up](https://www.meetup.com/learn-wordpress-online-workshops/events/297747513/)–`
   [Thursday, December 14th, 2023 08:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231214T0800)`
 * [Session 2 sign up](https://www.meetup.com/learn-wordpress-online-workshops/events/297748992/)–`
   [Friday, December 15th, 2023 00:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231215T0000)`

---

While these changes bring much needed refinements to the Training Team’s processes,
there’s always room for further improvements. If you have any feedback, feel free
to comment below, or [bring them up directly in the Training Team](https://make.wordpress.org/training/chat/)
any time.

---

Thank you to the following contributors who contributed to this project, either 
directly or by providing feedback as changes were implemented 👏🏼👏🏼 [@webtechpooja](https://profiles.wordpress.org/webtechpooja/)
[@jominney](https://profiles.wordpress.org/jominney/) [@sumitsingh](https://profiles.wordpress.org/sumitsingh/)
[@digitalchild](https://profiles.wordpress.org/digitalchild/) [@psykro](https://profiles.wordpress.org/psykro/)

Also, thank you [@milana_cap](https://profiles.wordpress.org/milana_cap/) for sharing
your insight from setting up workflows for the Docs team 🍪🍪

[#github](https://make.wordpress.org/training/tag/github/), [#procedures](https://make.wordpress.org/training/tag/procedures/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2023%2F12%2F05%2Frecap-github-updates-and-process-refinements%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/kaitohm/) [Kaito Hanamori](https://profiles.wordpress.org/kaitohm/)
5:30 am _on_ September 27, 2023     
Tags: [feedback ( 4 )](https://make.wordpress.org/training/tag/feedback/),
GitHub   

# 󠀁[Looking for feedback: Updates to GitHub issue templates and labels](https://make.wordpress.org/training/2023/09/27/looking-for-feedback-updates-to-github-issue-templates-and-labels/)󠁿

**Summary**: In an effort to streamline [the team’s GitHub repo](https://github.com/WordPress/Learn),
the [Next steps for GitHub updates](https://make.wordpress.org/training/2023/07/08/next-steps-for-github-updates/)
project is looking to reduce the number of GitHubGitHub GitHub is a website that
offers online implementation of git repositories that can easily be shared, copied
and modified by other developers. Public repositories are free to host, private 
repositories require a paid subscription. GitHub introduced the concept of the ‘
pull request’ where code changes done in branches by contributors can be reviewed
and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
issue templates in the repo from 9 to 5. The project is also looking for input as
the current list of 119 labels is reassessed and reduced. **Please leave your feedback
on the proposed changes by October 17th (Tuesday).**

## Please review the new list of GitHub issue templates

In an effort to streamline [the team’s GitHub repo](https://github.com/WordPress/Learn),
the [Next steps for GitHub updates](https://make.wordpress.org/training/2023/07/08/next-steps-for-github-updates/)
project has [identified a need to reduce the number of GitHub issue templates](https://make.wordpress.org/training/2023/07/08/next-steps-for-github-updates/#comment-3984).
The expected benefits from this change include:

 * Less confusion for contributors creating new issues.
 * Less redundancy during topic vetting. (Currently, Subject Matter Experts (SMEs)
   must vet the same topic for multiple content types.) 
 * Reduction in quantity and complexity of automations that will get set up.
 * Preparation for the consolidation of content types, as proposed in [Looking for Feedback: Learn Website Information Architecture](https://make.wordpress.org/training/2023/09/26/looking-for-feedback-learn-website-information-architecture/).

Below is a table listing the current 9 issue templates, and the 5 proposed templates
they’ll correspond to. Each of the new templates have already been created and can
be previewed from [https://github.com/WordPress/Learn/issues/new/choose](https://github.com/WordPress/Learn/issues/new/choose).(
Scroll to the bottom of the list, and you’ll see these new templates prefaced with“
_do-not-use_”.) Please leave any questions, suggestions, or other comments about
these templates below.

| Current issue templates | Proposed issue templates | 
| Bug Report Template
Content Feedback | Feedback | 
| Topic Idea | Content Development (general) | 
| Lesson Plan TemplateTutorial TemplateOnline Workshop TemplateCourse Template | Content Development (for Faculty) | 
| Content Translation Template | Content Translation | 
| Meeting Agenda Template | Meeting Agenda |

Some points to note in these changes:

 * All feedback pertaining to Learn WordPress, regardless of whether it is regarding
   the website itself or the content, will be submitted in one issue. [Automation similar to what the Docs team has](https://make.wordpress.org/docs/handbook/github-repository-and-projects/documentation-issue-tracker/#automatisation)
   will be set up, allowing any contributor (regardless of GitHub access) to triage
   and send these to their respective projects where they’ll be actioned on.
 * The current “Topic Idea” template will be renamed to clarify this is actually
   the issue content creators should use when creating content. These issues will
   be highlighted to SMEs to be prioritized in their topic vetting process.
 * Faculty who will immediately create content themselves may skip the vetting process.
   The four content templates the repo currently have are designed for this process,
   but weren’t labeled as such, and were therefore confusing general contributors.
   These will be consolidated into a single template marked “for faculty”. [Automation similar to what the Docs team has](https://make.wordpress.org/docs/handbook/github-repository-and-projects/documentation-issue-tracker/#automatisation)
   will be set up, allowing Faculty to call the respective development checklist
   for their content type with a command.

## Help us review the current list of GitHub labels

The project has exported the current list of GitHub labels into [this Google Spreadsheet](https://docs.google.com/spreadsheets/d/1XGJKG26N1T59dPM-G_oT6eI67mlgaaGV4YQm_XbGDqg/edit#gid=0).
We’re looking for Training Team contributors with experience in labeling issues 
in the team’s repo to help us document the purpose of each label.

Once completed, the project will:

 * Reassess labels based on their current use.
    - Similar labels may be consolidated.
    - Labels may be renamed for clarity.
    - Some project-specific labels may be replaced with [custom fields](https://docs.github.com/en/issues/planning-and-tracking-with-projects/understanding-fields).
 * Document the purpose of each label in the handbook.
    - Documentation will also include how new labels should be added and which labels
      are used in automation and, therefore, should not be modified.

## Thank you for your feedback!

We’re looking for feedback on the proposed changes to issue templates and documentation
regarding [the repo’s current list of labels](https://docs.google.com/spreadsheets/d/1XGJKG26N1T59dPM-G_oT6eI67mlgaaGV4YQm_XbGDqg/edit#gid=0),**
by October 17th (Tuesday).**

---

_[@webtechpooja](https://profiles.wordpress.org/webtechpooja/) and [@jominney](https://profiles.wordpress.org/jominney/)
were co-authors of this post. Thanks also go to [@yuli-yang](https://profiles.wordpress.org/yuli-yang/)
for exporting the list of GitHub labels for the project!_

[#feedback](https://make.wordpress.org/training/tag/feedback/), [#github](https://make.wordpress.org/training/tag/github/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2023%2F09%2F27%2Flooking-for-feedback-updates-to-github-issue-templates-and-labels%2F%23respond&locale=en_US)