Alright, so hello everyone and welcome to today's online workshop. Today we are going to walk through the rethink GitHub process update.
In the WordPress training team. And I'm Ben and thank you for tuning in.
So first of all, just to give a bit of background of what the training team is, why we use GitHub.
Etc. So the Wine Prince project is made up of many teams. So if you go to make dot WordPress at all and I'll drop this link in the Zoom chat.
If you go to make up WordPress the log, you'll see we have current nothing. It's 22 teams.
That contribute and make the WordPress software. So at the top you'll see we have like core, design, mobile, accessibility.
These teams work with the code of WordPress. So These teams also use GitHub. And But they use it a little differently to how the training team uses it.
So probably these themes are more div focused and so they use GitHub in the typical way.
W, if you come down, we have training. So training team. We don't use a lot of code.
So the way the purpose for GitHub for us is mainly project management. Not really pull requests and reviews and that but more just managing the projects we are working on.
So the training team. What does the training team do? The training team looks after the website learn.wordpress.org.
So I'll drop that link over here in the chat as well. So low low press, it is a a website that started a concert that started like 12 years ago.
But really got going during COVID. So for a long time, in-person meetups or gatherings were the the strongest place for wopis.
Users would learn and share information. During COVID, meet have stopped happening. We couldn't meet in person anymore.
And so that's when the project really started. Developing a loan WordPress website as a place where people can continue to learn and continue to share information and grow in their WordPress expertise.
So we're not gonna dive too much into the loan WordPress website, but if you're not interested in learning about WordPress, we have things here for beginning users.
Expert users, beginner developers, intermediate developers, designers. Contributors So, we have a lot of content here.
And, Yeah, we have a lot of content here. So. The training team is the team designated to manage and update the site with new content.
So just jumping back. Oh, yeah. We have 22 teams in the WordPress project. And the training team is the team that looks after learn WordPress.
So training is the team name, Learn is the website name. So if we click on the training title here, that takes us to the training team log.
And I'll drop this link in the Zoom chat as well.
So when you first come here, you'll you'll see this, welcome box open up like this.
There's a hide welcome box link in the top right here. So I'm going to close that for a moment.
Now there's lots of information on this website and I just want to point out 3 important links. The first one.
Is in the blue bar here, it says getting started. By clicking this, you were taken to the training team's onboarding program.
So if you're interested in loan workers, if you want to get involved and start contributing to content and reviews.
And at the end of today, I'll be talking about GitHub. So if you want to get involved, but that GitHub administration.
This getting started link is the best place to start. So that will give you an overview of how the training can communicate with each other.
And then the training team does a lot of things. And we have 5 areas of expertise or 5 areas where you can contribute to.
So this getting started program sort of helps you decide what area would be the best place for you to get started.
And guides you through that. It's about 30 to 60 min to get through the program and by the end you would have made your first contribution.
And you would have started contributing to the training team. So that's getting started. The second important link I'm in the highlight is the handbook link.
We'll open this in a moment. But basically this is where all the documentation about the training team lives.
So if you want to make a video tutorial, how do you do that? If you go to the handbook, we have a whole section about how to make video tutorials.
And it gives you step-by-step guidance on how to do that. Or if you want to host an online workshop like I'm doing right now.
How do you do that? That information is in the handbook as well. Or how does the training team use GitHub?
What are the workflows in place? What do all the labels mean? All this information about how we use GitHub.
It's all coming in the handbook. And so that's what we'll be looking at in just a moment.
So that's the second important link. Hey, finally, I also want to point out faculty members.
So, faculty members, members of the training team who have been vetted, and have state they will dedicate their time to helping the training team meet the goals it sets for that year.
So the training team we have lots of different goals and the faculty members, people who have said, I want to help with that.
I'm going to dedicate some extra time. And they help the train you can move towards that.
General contributors can also definitely help out with any of those calls. But the faculty members have just given a bit more.
Dedication and they have some requirements and expectations we would like to see from them. And then as a reward for that, they are also given some special access.
So when we look into GitHub today, There are some things anybody can do and there are some things only faculty members can do.
And that's the way the WordPress project has set GitHub. The WordPress project in general is open to anybody.
So anybody can come and contribute. But that means if anybody could do everything then somebody with bad intent could come into GitHub and for example mess everything up, break the word press code there.
And do bad things. And we don't want that. And so the way the WordPress project has said GitHub is that anybody can create issues, anybody can comment on issues, anybody can submit code.
But then people who can actually accept those or label those. Or move those between projects. That is limited to people with special access.
And in the training team, the people without access are the faculty members. So. If you start to get involved with the training team and your helping out with the admin stuff, there's a lot of acting things.
Non-faculty people can also do. And in your feeling like this is something you really want to get involved with.
They do apply to become a faculty member. By clicking on this it'll take you to resources it'll show you what what is expected of faculty members and then there will be an application form so if you want if you after today's presentation you listen about all the GitHub stuff and you want to get involved even more deeply and they do apply to become a faculty member.
All right, so that's a holistic field. How the WordPress project is made, what loan WordPress is, what the training team does, and sort of a very big overview of what the GitHub.
Access and things like that look like. Are there any questions that so far? We'll start diving into the details of the GitHub usage in the training team next, but I just want to pause and make sure everybody's clear with everything so far.
Okay.
Alright, no questions are coming in.
Okay. So let's move on. So let's click on handbook.
And this is the training team handbook and you'll see we have quite an extensive table of contents on the left here.
We have about, we have getting started, we have faculty program. Etc. What we want to focus on today is the how to guy who opened that And then under how 2 guys we have how we use GitHub.
So click that, open that page. And you'll see there are even more child pages under that.
So This is where we document how the training team uses GitHub. I'm not gonna rep everything today, but just to read out the titles, we have a page about the automated workflows.
I'll show some of those in a moment. We have a page about the GitHub labels.
And then we have a page about triology and content development issues. How do you triage content development issues?
And then another page about triaging content. Localization issues. And another page about validating and applying content.
And finally, a page about invading topic ideas. So the top 2 pages are really about how the GitHub is set up for the training team.
And then the bottom 4 pages here give you step by step walkthrough of the different processes. In the training team that use GitHub.
Okay, so just to refresh we came to the training team blog We clicked on handbook, we clicked on how to guides, and I finally clicked on how we use GitHub.
And I'll share this link in the Zoom chat. So folks can open it up. Follow long And if you're going to be working with GitHub in the training team often, I recommend book marking this page because there is a ton of resources here.
All right. So let me just read the first few paragraphs here. How we use GitHub.
How does the training team use GitHub? So the training team uses Hmm, that's, that's a mistake.
The training team uses the GitHub repository. WordPress slash learn to manage all of the following.
I'll open that up.
So this is the training team's GitHub repository. And you'll see here it's underneath WordPress.
So it's github.com slash WordPress slash loan. So if you click on WordPress, this will actually show you.
All the repositories. Inside the WordPress project. And there, 150 repositories.
So the WordPress project manages a hundred 50 repositories. That is a lot.
And the load project is just one of those. So the training team. We just focused on the loan repository.
We leave the 149 others for other things. We do everything we do in the Learn repository.
Alright, and then at the top here, so this is like the homepage of our repository.
You'll see we have issues. The training team currently has 490 open issues.
And, that's a lot. The training team moved to GitHub.
2 or 3 years ago. So you'll see in the 2 or 3 years we've closed 1,183.
So congratulations training team. That's a lot of issues. And you'll see we have 490 issues open right now.
Okay. So let's go back to the handbook and let's read the next section. So the train team uses this GitHub repository to manage all of the following.
So first of all, the code for learn. Dot WordPress at log. The loan WordPress website we have a look before here.
The cold for this website. Lives in the Learn WordPress repository, GitHub repository.
So that part is similar to how other development teams use GitHub. We have all our site data inside the loan repository.
And so for that, for that website code. We do have developers who make pool requests and review each other's full requests and then.
They merged that and they create branches and all these development type stuff. So that does happen in the loan repository.
But we have all these other things that are also happening there. So the second point, we track content development issues for loan WordPress.
So every piece of content that is published on loan WordPress has a corresponding GitHub issue.
And the process of that piece of content getting developed is all tracked in that GitHub issue.
So we have the code for the WordPress website and then we have GitHub issues for each piece of contact.
Then thirdly, each. Content translation, translation is also attracting one WordPress.
That we have issues tracking every piece of content being translated into different languages. That all has its own issue and is tracked in this repository.
Then issues tracking content, topic ideas for a moment. So before a piece of content is published on the website, it goes through a few stages.
The first stage is somebody comes up with a topic ID and they submit that topic idea to the team. So for example, somebody says, I want to make a tutorial video about the 2,024.
So they submit that as a topic. That thing goes through a bidding process. So we have a role called subject matter experts in the training team.
These subject by the experts have a look at those topic recommendations or suggestions. And they just make sure those topics are relevant and they vet the topic ideas.
So is it something important to the WordPress community right now? Is it a priority? Is it something the training team should be spending resources?
Time and answer to develop. For example, if somebody said I want to make a tutorial about the 2016 thing.
Now that's like from 8 years ago. So that even quite relevant. Right now on the loan web website.
So we would probably say that topic. Isn't a good fit for the site. So the subject matter expert, topic ID.
And that all happens in GitHub as well. Next, we have issues tracking admin part of the training team, so different administrative things attracting get time.
And finally learn WordPress site, content feedback and other communication from learners. So if different people are going through content on learn and they find a bug like There's a button on the website where they click and they can't click it.
Or maybe they found an outdated screenshot in a piece of content. Or maybe they just have an idea to make the website better.
Any of this feedback people have they can also submit to GitHub and that is where we look at the feedback and then decide whether we're going to apply it or not.
So, that is a lot happening in the training team's GitHub repository. We have code for the website.
We're tracking content development. We're tracking content translations. We're vetting topic ideas, we're tracking admin task.
And we're also looking at feedback that users provide to us.
So. That is a lot and Basically, when the training team migrated to GitHub 2 or 3 years ago, That was all being done in one location inside GitHub.
It was all done in one place. And so that was very confusing. The training team had like, 120 something labels they were using to label issues, move things around.
And it was just computing it was a big minute. Hey, over the last year or 2, the training team has been slowly hiding on the GitHub repository and making it easier for people to understand and contribute to.
And one way we've done that is by using a feature in GitHub called Projects.
So I've come back to the Learn, GitHub repository and I'll click on projects.
And you'll see we had 490 issues, not a lot. But we've split those up into 7 projects.
So the training team has 7 projects. And each of these are called project boards. For the first project board, is Learn WordPress content localization.
So, all, issues related to localization or translation. In this localization project board. The next one is learn WordPress content feedback.
So any feedback we get from users is inside the feedback project board. Then we have a project board for training team administration.
We have a project board for the website development. So that's like code that would learn WordPress.
We have one for content development. We have one for topic vetting. And finally at the bottom we have one for learning pathways project.
So we won't go into too much detail about this last one, but just to give everyone a sneak peek.
We are currently in the process of redesigning the loan WordPress website. For a brand new launch next year.
The goal is to get this done by July. At the moment this is what the LoneBURG, PAST LIKE website looks like.
And as I mentioned before, COVID happened all of a sudden. And so all of a sudden the project started building out the low marketers website putting lots of content in.
And and, they just wanted to get the fight going. Then that the site has been going.
And that COVID is pretty much finishing. The WordPress project is reviewing the long WordPress website and figuring out how this website can continue to exist and best serve the WordPress community.
So we are in the process of redesigning the website. Redesign the information. Architects in the website, considering what content we should publish, etc.
There's a whole big redesign going. On right now and that is our track in the learning pathways project.
So. Yeah, so you won't probably have to go into this project too much and but yet to know those issues that all managed in this project board here.
So the the training team has 490 issues but to be honest you won't need to click on this issue tab very often.
Probably you will want to click on the project at first and then click on the project you want to contribute to then.
So for example, Let's have a look at the content development project. Oh, and I will say the order of the project.
Board listed on this page will change. I think GitHub puts the most recently updated project board at the top.
So don't be surprised if you come to this page and you see the project called listed.
All right, so let's go to the content development project board. And let me pause there. Are there any questions so far?
Hopefully I haven't lost anyone, but is there anything you need to clarify? Or is everything good so far?
Courtney, thank you for the Alright, okay. So this is what the project board looks like. And, there are a few things you'll notice.
First of all, we have columns. That go like this. And then we have tabs at the top of the page here.
So the columns, rim, represent the status of an issue. And issues move from the left column right through to the right column.
So we are looking at the content development project. So whenever a piece of content gets developed, it goes through these data.
First of all, it's in ready to create. To this this is letting people know anything in this column is really for people to pick up and react.
The topics here have all been written by our subject matter experts so we know they are relevant to the WordPress community right now and we're just waiting for content credits to pick this up and start working on that.
So we have 82 issues in this column right now. When somebody says, okay, I'll make this.
That issue is then moved into the draft and progress column. Oh, we know there are 52 items, different people are working on right now to create.
One the piece of content is created, it then moves into the ready for review column. So every piece of content that is published on learn.
Is open for review for 2 weeks or until they get 3 reviews So everything in this column here is waiting for review.
Once the reviews have completed, it then moves into a brand new column. So this column is something new that was made.
In the last 2 weeks, it moves into preparing to publish column. So until now. Even after a piece of content had enough reviews, it would still stay in the ready for review column until it was published.
And so like, well, videos are being made or subtitles were being created. And so what we saw were people were adding more and more reviews on the piece of content.
Even with even though that was already ready and reviewed and there were other pieces of content that weren't getting the reviews done.
So we've made a brand new column here preparing to publish. So on the piece of content has received 3 reviews, it moves into preparing to publish.
And then once the content creator has finally published the item, it moves into published or closed. So you can see he issues move from one column to the leg, to the row.
And clicking on these tabs at the top, this will give you a quick view. Of all the issues in that column.
So at the moment we see 10 items. Review, you have to scroll a bit to see all that.
But if you click on ready for review up here, then they're all shown right here and you can even see the review stage.
So we can see these 3 pieces of content. Have already had their first review. And you'll see this will go to second review and review complete.
As the different reviews have happened. And you'll also see the content time listed here. So. This one's a Latin, these are tutorials, we don't have a lesson plan up here waiting to be reviewed.
So for example, if you want to review content for the Lone WordPress website, that the best place to go would be this tab here.
So although, GitHub. Repository has 490 issues.
I'm searching through those to find the issues that need a review can be quite difficult. But if you come to the project board and then click on the ready for review tab, then you'll see all the 10 items waiting for a review right now.
So hopefully that gives you a picture of why these project boards help us. Manage all these different types of content on our platform.
So that was content development. Let me quickly open content localization. And you'll see this is.
Set up in a similar way so we have a waiting triage on the left. Translation in Progress.
Ready for review, preparing to publish. And then publish the clothes on the right. In sport localization at the top here.
We actually have tabs for each language. So for example, if we click on, let's see, This will show you all the Bangladesh issues.
And what status they are currently in. So we see there's one issue. Translation in progress.
One is in ready for review, one is in preparing to publish and 2 are under looking for translator.
And so each project both set up a bit differently, but they set out to hopefully help the contributors, contribute to their area of expertise for most.
Effectively.
All right, so going back to projects, content organization, content development. Etc.
Alright. Any questions about that?
Coming back over here. So that is how you can find currently old issues. How do you create a new issue?
So for example, oh, Laura. You have a hard time navigating to the Learn page.
I presume you're talking. This one? This to another page. This page.
I have a hot key set on my computer which I can press and that takes me to to the GitHub repository.
So you see right now I just opened this project. I have a hot case set on my keyboard so that I press that and it takes me right to get up.
I think the easiest thing is to bookmark it. Bookmark this page. If you really want to go to it manually, then it is linked in the training team's handbook under how we use GitHub.
There's a link here. And also in the welcome box. We have a link here to how we use GitHub.
So that is a bit of a shortcut to get to the GitHub. Yeah, Laura, you have, you have used bookmark.
But yes, I have a hot key on my, on my computer because as you say, it is difficult to get to.
It takes a few clicks. So, yep.
Alright, so we know how to find the project. B, how to find issues in the project board.
But how do you submit a new issue to the load? Repository. So to do that, you would go to issues.
And then at the right, you'll see new issue. And, by clicking this.
We are given 5 templates. Now the training team used to have 9 templates. So this is another one of the updates recently.
We reduced the 9 templates down to 5 templates. Having more option was just computing people.
So we, the options a bit and streamlined the issue creation process. So we have 5 different templates here.
We have one for feedback. So if somebody finds a bag on the loan WordPress website if they find content errors out there, you can or if they have feature requests.
These all go into the feedback issue. Next, we have content development in general. So generally when the contributor wants to make content, they would start with this one.
And when they, they'll ask them to submit a topic and then once they submit a topic, the subject matter expert, that's that.
And then once it's been vetted, they can start building out the content. So this is the general content development checklist.
Now we have a third one here, contact development for training team faculty. So because the training team faculty are people who have already been vetted they can skip the topic.
Vetting process when they build content. But that's one of the privileges of becoming a faculty member.
Their responsibilities becoming a faculty but there are also some privileges And one of those is they can skip the topic.
Betting process. So the third issue is designed specifically for the faculty members. Who build down content and it skips the topic backing for them.
Then fourth, we have content translation. So if anybody wants to translate content, you would start with that issue.
And then finally meeting agenda. So the training team has weekly meetings. Currently the meeting agenda is a made by the team rest so people won't generally need to use this one, but having this issue can make it easier for the team reps to write their ejectors.
So we had 5 different issue templates. And I'm going to create a feedback template.
But at the moment I have logged into my faculty account. So you'll see my face on the left here.
As the faculty, I have some special access and things which could be confusing. I'm going to switch right now to my non-faculty account.
So this is the same page with the 5 issue templates and you'll see here it's it's like a an anime comic of myself.
This is my non faculty GitHub account. So let me show you what creating an issue looks like as a non-faculty.
So let's click getting started. And at the moment we use the feedback one. So as a general contributor, the WordPress project has restrictions.
Did you know contributor can't assign an issue? They can't label issues. They can't add issues to projects.
Etc. So you a general contributor can't edit any of the things in the so what we would do is, we'll give our feedback a title, feedback.
This is a test. Or a online workshop. Alright, and then we come down and we give ourselves a description.
So what does the template say? Thank you, for the meeting feedback to the weather training team.
You can see if similar feedback has already been reported by searching this link here. So If you're familiar with GitHub, you can go to that link and search the if anybody else has committed the similar feedback.
But let's go move down and see what, see what's written here next.
So type of feedback. Now this is something new we introduced in the last 2 weeks. So, please type the corresponding command that represents your feedback.
It will be too flashes. Followed by a word, dev content or handbook. So is your feedback reporting a bug of feature requests for the Lone Worker's website?
Type slash. Is your feedback about the content on longer press such as reporting outdated information? Type slash slash content.
And finally, is your feedback about the train teams handbook or other documentation? Type slash handbook.
All right, so. This is one of the automations we recently set up in the GitHub repository.
So I mentioned before the general contributor they can't add labels or move put issues into project etc.
This is a WordPress organization restriction. So it's not just the training team. It's in other teams as well.
But, so that means like until now when somebody makes a new issue. It just gets dumped in that 490 issues list.
And somebody from the faculty had to come through and triage that regularly, move that to, add labels, remove labels, move them into projects, etc.
So the team recently said up a automation. Where you would type a code when you submit this issue.
And then that code would automatically put the issue in the right project board. So it's sort of like a workaround because We're giving contributors the ability to put issues in the correct project even though they don't have access to either things on the right here.
So, Laura, your question is, where do you type it? Before after the arrow?
The answer is anywhere. You can type it anywhere because the automation all it does is it looks through the entire text of the issue.
And if it finds that string that that that command anywhere it will run the command. So I'm going to type it after the arrow here but you can type it before you can even type it within another word.
And if you have that the exact string the workflow will run. So at the moment, let's try.
Let's try content. Let's say we found some outdated information. In one of the lessons on learn So we would type slash content.
And then there's a section here too. Give a bit more. Details. And step by step reproduction of how to reproduce it, etc.
So there's other information you can give you. But basically what I what I wanted to showcase was this command.
So you could put the content there, you could put it at the very bottom, you can put it inside.
The comments here like this would work as well.
All right, and let's press submit. So submit new issue.
Now, GitHub workflows happen after you've in addition and take about 10 s or so.
Do you still have to pause for a little bit here? But what will happen is you know this right now I wasn't touching anything.
But it added the content feedback label. And then you've added this to the Learn Workers Content feedback project board.
And it even moved it into the awaiting validation. Status in the content feedback protocol. So all I did was I use the flash slash content command in the issue.
And It added the label, it added the project, it did all that for me. And that is one of the new features we recently set up on.
Hiccup. So general contributors can now also help with triaging issues when they submit it.
Laura, you say I always thought that I had to delete the directions and type in my. Okay.
You'll notice the directions aren't listed here. Let me edit my issue again.
So this bracket, this. Triangle, to here. This is a comment. So this is this comments out.
Anything written between these 2 brackets. So anything written between these 2 will not show in the final issue.
So that's, that's how GitHub does commenting. So yeah, you don't have to delete all that.
You don't have to delete all that and, It just won't show.
Alright, so something else I want to show is for example Let's say you type slash content and you submitted this issue.
But you go, you know what? This isn't a content issue at all. This is actually a feature request for the website.
So I should have like I should live type slash slash do. What you can do is you can add a new comment.
And type oops slash, dev. And commit that. And the automation will run again in the background.
And just wait 5 s 10 s while that is working in the background and you'll see It now has the 5 buck label added.
And this was added to the learn website development project board. So these magic automation commands can work inside the issue itself.
You can also work inside the comment. So a general contributor if they're treeing issues. If somebody has accidentally put an issue in the wrong project board, they can also use these comments to move the issue into the correct project board.
So I thought that was pretty cool. The one thing at the moment is, Even though it added that bug and added it to the website development project board.
It didn't remove it from the old project board. So This automation is actually only 90% complete and It will probably be another couple of weeks before it's finally completed, but ultimately what I hope to see here is when somebody type a second command.
It is removed from the first project board and added to the second project board as well. At the moment, a general contributor come through that.
So if something like this happens, you can ping a faculty member. But let me jump back to my faculty.
Account and the faculty member can. Remove labels. I can remove that label. And also remove it from project boards like that.
So, a faculty member can do that for folks. But you, so that is one of the automations we set up.
Where can you read more about these automations? So we have created a new handle page. So I'm back in the training team handbook and the help we use GitHub.
We have automated workflows. And this live, the 3 different workboats we currently have set up.
So we have add a content development checklist. We have labeled and triumph feedback issues.
And we also have self assign an issue.
Alright, so we just looked at the content feedback. Commands. Let's say let's say you go to a project.
The content development.
And let's say you want to work on this lesson. So. Use Duatel filters to change color effects lesson plan.
Alright, so this is in the ready to create we're looking for somebody to create this. And you have a look at this and you go, you know, I think I want to make this one.
Until now, general contributors Could not assign issues to themselves. So what they would have to do is they would have to add their name in the GitHub issue and then ping a faculty member and then the faculty member would assign the issue.
For them. Now. Contributors all they have to do is type assign in a new comment. Oops.
My screen is just a bit small. Here we know. Type a sign in a new comment. Press comment.
And then we need to let the workflow run in the background for 5 10 min but just wait.
And hopefully this will add me. As an assigning.
It should work.
Did I spell that right?
Assign.
Alright, it's not happening. That's live, live TV for you, I guess.
So let me check. Will it automatically refresh? Oh, that's, that's the thing.
Let me refresh.
Oh, there we go. Okay. So you have to you have to refresh the page I guess for this one.
Huh. So. You can now see this has been assigned to me and it also has the self-assigned label.
So that label helps us know which issues folks have assigned to themselves. Let me open that up over here.
So you see there are 2 views here. You can look at an issue. At the moment, we're in the project board view.
Where the issue sort of popped out from the right it didn't automatically update there. But if you click on the title that will also take it to the issue itself.
And you'll see at the bottom here. Okay, so I assigned myself and then there was a new comment.
Hi based on events. Thank you for your interest in this issue. If you have any questions, do not hesitate to ask them in our training.
Site channel. Thank you for contributing. So that's a bit of a nice welcome message from the GitHub bot.
Now, let's say for example, this issue was already assigned to me. And but this different contributor over here.
Also try doing the self-ethone to themselves. So you see that was my faculty account that defined that.
I'm back in my non-faculty account and let me try doing a sign.
Let's see what happens.
So again, it might take about 5 s.
Okay.
There we go. Okay, Hi, Nicole, you could be it on. This issue is already assigned to be some.
A faculty administrator can also add you to the list of assignments or swap you with the current assignment.
Or you can take a look at the other assigned issues we have. So the workflow actually takes a look and sees if somebody has already been assigned to this issue or not.
Before either signs the next person. So. At the moment, For example, if this person becomes inactive and we want to reassign the issue, then you would have to reach out to a faculty member who can switch their assignments around.
But if the issue isn't assigned to anybody, then any contributor can now self assign the issue to themselves.
So I'm just gonna clean that out.
All right. And then one final workflow I wanted to show. So coming back to automated workflows We just looked at label and triage feedback.
Issues, self-assigning issue. We also have one set up at a content development checklist.
Now this one is specific to faculty members. So I mentioned before, okay, let's come over here.
Let's create a new issue again. And we have a content development issue for general contributors and we have one for training team faculty members.
Now the general contributor, they, their issues go through a topic vetting process and the once it's invented you're given instruction to copy and paste a content creation checklist into your issue.
But for faculty who we have some faculty members who create. One or 2 pieces of content every week.
Going to copy going and copying pasting that checklist can be a bit time consuming.
So we've set up an automation for faculty members. So let's see, for example, they're making a lesson.
And the content title is my first lesson. Or something like that. And then we have decount, so content, I, content title, public description, etc, etc.
Learning objectives, etc, etc. And then we have finally automation code. So similar to how we triumph feedback, Under this comment, types 2 slashes.
Followed by the content. Tutorial, online workshop, list and plan or course. Once submitted that code will add a new comment to the issue with the relevant development checklist.
So let's say this was a Listen plan, listen. Plan. What the faculty need to do is type slash lesson plan.
And then submit the new issue.
And a few different things happen here. So.
Let's go.
Here we go. So then that added the lesson plan development checklist to the issue. So the faculty member doesn't have to go and copy and paste the checklist.
They can just click on different items once it's being completed.
So that is the third workflow we've set up. In the training team project.
All right, so we're coming up at the end here. So if you had any questions or things you want me to demonstrate again, type in the Zoom chat.
As you wrap up, I'll just briefly show. We have a page here. That documents all the different GitHub labels.
Now labels are added here to an issue. Until now, for example, let me create a new piece of content.
We've had to add a label. About what the content type is, what the audience is.
What the experience level is. So a single issue would have had like 7 or 8 or 9 labels.
Which is quite confusing actually. So what we've done recently is we IA lot of these labels and turn them into custom field.
So what does that mean? So if you're a content developer again, this is, specific to faculty.
So the general contributor, you'll need a faculty to set the custom field for you. The goal is to have automation for this as well, but it's not quite built yet.
So hopefully down the line will have more to introduce. But for the moment. For example, this is a piece of content.
So the faculty. Member will want to add this to the content development project board.
Then underneath the content development you'll see we have a status. So if I'm building this, I would put this into drafts in progress.
And then next to that you'll see plus 6 more. Clicking on this shows the different custom field.
You can apply to this issue in that project. So if you have been a content developer with the training team.
Seems. 2 weeks ago, or longer, then you would have been adding different labels to the issue, but now you don't have to do that.
Most of the things you want to set are custom fields. So review stage, how far has this gone in Reviews?
We're not allowed to review it so we can leave it as is. Content type. So this is a lesson plan.
Topic. And this will be Let's say it's about the training team. May audience. So you see audience and experience were listed in the issue itself.
You can type that over here. So this is for let's say contributors, experience level, any and WordPress.
Persian with most recent updates. So this isn't applicable, so we'll leave that at it.
So by stitching all these as custom fields. We haven't, we didn't need to set any labels on there.
Now, the awaiting triage. Because I'm a faculty member. The waiting triage means this issue is still waiting for cut them fields.
It's waiting to be added to the right project and it's waiting for in a tiny and the 24 customer field.
Say if I find the issue to I've set the different cuts in field. I can then remove the awaiting triage label.
And now, typically, content development issues don't need a single label. So if you come back to the content development project board.
You'll see some of these have a priority label on them. But the white ones are the custom fields.
And by moving from labels to custom fields not only will be able to reduce the labels in the training team repo.
But we've also made the interface a lot like cluttered. Until now we would have had like 8 or 9 labels on each of these issues which just made it too complicated to look at.
So custom fields. So the training team still has 27 labels which are used for very specific cases.
Many of them are used for development related things. So if you're not a developer, then you probably won't need to use many of these labels.
But if you're interested to know what the labels are used for, then we have a handle page here that lists the 27 labels used in the training team.
Oh, right. So we went through a lot today. I gave an overview of how we used the GitHub.
Project boards, to manage training team. Things. We looked at how to create new issues.
The different automations that are set up and how you can use the automation codes in your issues and comments to do different things.
We talked a little bit about the access differences between faculty members and general contributors. And then we also talked about some faculty specific things like custom fields.
I think I've covered all the recent updates to the training team's GitHub repository.
There was a lot of information. Are there any questions or comment to that other even? Maybe you want me to show something again.
Does anybody have any comment?
Okay.
Eagle at the beginning, you said you wanted to look at some WordPress GitHub processes.
You want to know how the WordPress project uses. GitHub. Hopefully this gave you an idea of how the training can use this GitHub.
Yep, and John, you said you wanted to see what's behind the curtain. Did that give you a good idea of what's behind the No, hold the recording site.
Courtney you say you haven't used workloads yet but it seems pretty straightforward Great. For example, that self-assign workflow, we still have to incorporate that into our onboarding program.
It's not really No, like we're not identifying a new users yet about it because it's brand new.
I've sort of been testing it for a while. But now that we know it works, I think we can incorporate into our own boiling.
So all our new contributors know they can self-asign issues to themselves.
Eagle, the project flow is new to you. I'm glad you learned something new. Tracy, you learned a lot about the new updates.
Laura, you're not scared this much. That's good news. And Laura, thank you for simplifying the library.
Yes, oh boy, we had like 130 labels. Which was just overwhelming and confusing.
Even for the experienced user. For the recording sake I just want to finally point out. Where do these automations live?
So if some, if there's a developer out there who wants to help us build out these final bits of automation.
And you're more than welcome to join us. I would love to work with you. Automation files live in sorry github So I've come back to the main page, you click on GitHub.
And then you click on workflows and all our workflows live here. You'll even see that the file code incomplete workflows because there are still things that need to be created.
And if you run a workflow and you're like, huh, has it happened? Jen, has it, has it worked?
You can click on the actions tab here next to project. You click on actions. This keeps a record of all the automated workflows that ran in the background.
So something doesn't look like it's working, developers will go to the actions, and click on the actual workflow.
And see what in the workflow didn't. Run as expected. So it's good to know because all of this is recorded in GitHub.
So if there's ever a bug, we can go in and debug it and fix things.
So yeah, if anybody's interested in helping out with that, I would love to have you join our efforts.
All right, final question. Eagle off topic. Do you know how the make that workers learn menu is created?
May. How you talking about this menu?
Got make up one question. Are you talking about the menu on this web? On this website.
On make WordPress. So let's go to
This page.
We're training.
This is to make a WordPress a little training. This tab is made.com.
Okay, we're at times. So I'll continue this and zoom to answer your question, Eagle, but for the other folk.
Thank you for joining us. And if you have any questions, you can find me in the WordPress slack.
Instant. So feel free to reach out to me there and I'd be happy to answer questions even after this session.
Is over. I'm Eagle, I'll be here for a couple more minutes. I can post the recording and we can go through your question together.
Then. All right, but thank everybody for joining and I look forward to seeing you in another online workshop in future.
Have a good time.