 All right, so hello everyone and welcome to today's online workshop today We are going to walk through the written github process updates 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 a background of what the training team is why we use github Etc. So the WordPress project is made up of Many teams so if you go to mate.wordpress.org and I'll drop this link in the zoom chat If you go to mate.wordpress.org You'll see we have current nothing. It's 22 teams That contribute and make the WordPress Software at the top here. You'll see we have like core design Mobile accessibility these teams work with the code of WordPress So these teams also use github But they use it a little differently to how the training team uses it So probably these teams are more dev focused and so they use github in the typical way Whereas if you come down we know 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 learn WordPress and it is a Website that started a concept that started like 12 years ago But really got going during COVID so for a long time in person meetups or gatherings with the the strongest place where WordPress users would learn and share information But during COVID meetups stopped happening We couldn't meet in person anymore. And so that's when the project really started developing the lone WordPress website as a place where people can continue to learn it continue to share information And grow in their WordPress expertise So we're not going to dive too much into the lone WordPress website But if you're 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 over here 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 And 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 have you'll see this welcome box often up like this There's a hide welcome box link in the top right here So I'm going to close that for the moment Now that there's lots of information on this website and I just want to point out three important links The first one is in the blue bar here. It says getting started by clicking this you would taken to the training team onboarding program So if you're interested in learn WordPress, 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 with that github administration, this getting started link is the best place to start So that will give you an overview of how the training team communicates with each other And then the training team does a lot of things And we have five areas of expertise or five 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 minutes 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 up on the highlights is the handbook link And 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 is also in the handbook And so that's what we'll be looking at in just a moment So that's the second important link And finally, I also want to point out faculty members So faculty members are members of the training team who have been vetted And have said 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 are people who have said I want to help with that I'm going to dedicate some extra time And they help the training team move towards that General contributors can also definitely help out with any of those goals And 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 Um, so when we look into github today There are some things anybody can do and there are some things only faculty members can do Um, and that's the way the wordpress project has set github up 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 wordpress code there and do bad things And we don't want that And so the way the wordpress project has set github up 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 with that access are the faculty members So if you start to get involved with the training team and you're helping out with admin stuff There's a lot of admin things Non-faculty people can also do And you in your feeling like this is something you really want to get involved with Then 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 then do apply to become a faculty member All right, so that's a holistic view How the wordpress project is made what learn wordpress is what the training team does It's sort of a very big overview of what the github Access and things like that look like Are there any questions there so far? We'll start diving into the details of the github usage and the training team next but I just want to pause and make sure everybody's clear with everything so far All right, 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 guide to open that up And then under how to guides we have how we use github Um, so I'll 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 Um, I'm not going to read through everything today. Um, 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 Um, and then we have a page about triaging content development issues How do you triage content development issues? And then another page about triaging content localization issues And then another page about validating and applying content feedback And finally a page about vetting topic ideas So the top two pages are really about how the github is set up for the training team And then the bottom four 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 along And if you're going to be working with github in the training team often I recommend bookmarking 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 That's a 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 teams github repository And you'll see here it's underneath wordpress. So it's github.com slash wordpress slash learn So if you click on wordpress, this will actually show you all the repositories inside the wordpress project Um, and there are 150 repositories. So the wordpress project manages 150 repositories. That is a lot And the learn project is just one of those so the training team We just focus on the learn repository. We leave the 149 others for other things We do everything we do in the learn repository All right, and then at the top here, um, so this this is like the home page of our repository You'll see we have issues um, the training team currently has 490 open issues And i'm that's a lot. Um The training team moved to github Two or three years ago So you'll see in the two or three years we've closed 1183 issues 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 training team uses this github repository to manage all of the following So first of all the code for learn dot wordpress at all The loan wordpress website. We had a look before here The code 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. Um, and so for that for that website code We do have developers who make pool requests and review each other's pool requests and then They merge 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 content Then thirdly Each content translation Translation is also tracked in one wordpress So we have issues tracking every um piece of content being translated into different languages that all has its own issue and is tracked in this repository And then issues tracking content topic ideas for loan wordpress 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 idea and they submit that topic idea to the team So for example, somebody says I want to make a tutorial video about the 2024 theme So they submit that as a topic idea That thing goes through a betting process So we have a role called subject matter experts in the training team These subject matter 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 effort to develop for example, if somebody said I want to make a tutorial about the 2016 theme Now that's like from eight years ago. So that isn't quite relevant Right now on the learn wordpress website. So we would probably say that topic Isn't a good fit for the site So the subject matter experts vet topic idea and that all happens in github as well Next we have issues tracking admin part of the training team to different administrative things attracting github And finally learn wordpress site bugs 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 Um, 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 for much So that is a lot happening in the training teams github repository We have code for the website. We're tracking content development. We're tracking content translations We're vetting topic idea. We're tracking admin task And we're also looking at feedback that users provide to us um So that is a lot and basically when the training team migrated to github two or three 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 um And it was just confusing. It was a big myth And so over the last year or two 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. That's a lot. Um, but we've split those up into seven projects So the training team has seven projects They usually call project boards for the first project board is learn WordPress content localization So all our issues related to localization or translation are 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 of work learn WordPress We have one for content development. We have one for public 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 learn 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 learn WordPress 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 learn WordPress website putting lots of content in And um, they just wanted to get the site going Then that the site has been going and that covered 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 architecture of the website Reconsidering what content we should publish etc. There's a whole big redesign going on right now And that is all tracked in the learning pathways project so Yeah, so you won't probably have to go into this project too much But just to know those issues are all managed in this project board here so the learn 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 tab first and then click on the project you want to contribute to there Um, so for example, let's have a look at the content development project board 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 board listed in a different order 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 me to clarify or is everything good so far? Courtney, thank you for the thumbs up All right 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 They go like this And then we have tabs at the top of the page here Um, so the columns represent the status of an issue And issues move from the left column right through to the right column Um, so we are looking at the content development project board So whenever a piece of content gets developed, it goes through these statuses. First of all, it's in ready to create So this this is letting people know anything in this column is ready for people to pick up and create 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 creators to pick this up and start working on it 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 in progress column So we know there are 52 items different people are working on right now to create Once the piece of content is created it then moves into the ready for review column Um, so every piece of content that is published on learn Is open for review for two weeks or until we get three reviews So everything in this column here is waiting for a review Um, 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 two 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 while videos were being made or subtitles were being created Um, 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 once the piece of content has received three 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 next um to the rough 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 ready for 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 three 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 I've listed here. So this one's a lesson 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 Then the best place to go would be this tab here Um, so although our 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 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, um, let me quickly open content localization And you'll see this is um 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 or closed on the right And for localization at the top here We actually have tabs for each language. So for example, if we click on let's see bangler This will show you all the bangler issues um And what status they are currently in So we see there's one issue um translation in progress One is in ready for review. One is in preparing to publish and two are under looking for translator Um, so each project board is set up a bit differently, but they're set up to hopefully help the contributors Contribute to their area of expertise most um effectively All right. So going back to projects um content organization content development Etc. All right Um any questions about that coming back over here So that is how you can find currently open issues Um, how do you create a new issue? So for example, um Oh Laura you have a hard time navigating to the learn page I presume you're talking This this one this page or another page this page I um, I have a hot key Set on my computer which I can press and that takes me to the learn um GitHub repository. So you see right now. I just opened this project tab I have a hot key set on my keyboard. So when I press that and it takes me right to github I think the easiest thing is to bookmark it Um 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 Um, we have a link here to how we use github So that is a bit of a shortcut to getting to the github Yeah, laura you have you have used bookmark um 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 All right So we know how to find the project boards how to find issues in the project board But how do you submit a new issue to the learn repository? um So to do that you would go to issues And then at the right here, you'll see new issue um And um by clicking this We are given five templates Now the training team used to have nine templates. So this is another one of the updates recently We reduced the nine templates down to five templates um Having more auction was just confusing people So we reduced the options a bit and streamlined the issue creation process So we have five different templates here. We have one for feedback So if somebody finds a bug on the learn WordPress website, if they find content errors outdated content or if they have feature requests These all go into the feedback issue Next we have content development in general So generally when a contributor wants to make content, they would start with this one And when they it'll ask them to submit a topic and then once they submit a topic A subject matter expert vets that and then once it's being vetted They can start building out the content. So this is the general content development checklist Now we have a third one here content development for training team faculty So because the training team faculty are people who have already been vetted um They can skip the topic vetting process when they build content So that's one of the privileges of becoming a faculty member Um, their responsibility is becoming a faculty But there are also some privileges and one of those is they can skip the topic vetting process So this third issue is designed specifically for the faculty members Um, who build down content and it gives the topic vetting for them Then for that, we have content translation Um, 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 Um, currently the meeting agendas are made by the team reps. Um, so people won't generally need to use this one But having this issue template makes it easier for the team reps to write their agendas Um, so we have five different issue templates And I'm going to create a feedback template But at the moment I've logged into my faculty account. Um, so you'll see my face on the left here As a faculty, I have some special access and things. Um, which could be confusing But I'm going to switch right now to my non faculty account So this is the same page with the five issue templates and you'll see here It's like a an anime comic of myself. Um, 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, um, the WordPress project has restrictions the general 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 right here Um, so what we would do is we would give our feedback a title feedback This is a test or a online workshop All right, and then we come down and we give ourselves a description. So what does the template say? Thank you so for submitting feedback to the website 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 if anybody else has submitted similar feedback Uh, 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 two weeks So please type the corresponding command that represents your feedback. It will be two slashes Followed by a word dev content or handbook So is your feedback reporting a bug or feature request for the Loan WordPress website? type slash slash Is your feedback about the content on Loan WordPress, such as reporting outdated information type slash slash And finally, is your feedback about the training team's handbook or other documentation type slash slash handbook all right so This is one of the automation 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 um teams as well but So that means like until now when somebody makes a new issue It it just gets dumped in that 490 issues lift And somebody from the faculty had to come through and triage that regularly move that so add labels Remove labels move them into projects, etc so the team recently set 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 edit things on the right here So lori your question is where do you type it before or 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 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 Um in one of the lessons on learn so we would type slash slash content And then there's a section here to give a bit more details And a 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 comment here like This would work um as well All right, and let's press submit um So submit new issue Now github workflows happen after the mid-diction it takes about 10 seconds or so So you still have to pause for a little bit here um 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 um learn WordPress content feedback project board And it even moved it into the awaiting validation status In the content feedback project board So all I did was I used the slash slash content command in the issue um, and It added the label it added the project etc did all that for me And that is one of the new features we recently set up on github 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 stuff. Okay Um, we will notice the directions aren't listed here Um, let me edit my issue again So this bracket this triangle exclamation hyphen hyphen To here this is a comment So this is this comment out anything written between These two brackets So anything written between these two will not show in the final issue Um, so that's that's how github does commenting. Um So yeah, you don't have to delete all that. Um, you don't have to delete all that and um It just won't show All right. So something else I want to show is for example For let's say you type slash slash content and you submitted this issue But you go, ah, you know what this isn't the content issue at all This is actually a feature request for the um website So I should have I should have typed slash slash do What you can do is you can add a new comment and type oops slash slash do and submit that And the automation will run again in the background And just wait five seconds ten seconds while that is working in the background and you'll see It now has the type bug 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 a comment So a general contributor if they're triaging 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 um I thought I thought that was pretty cool um, the one thing at the moment is um Even though it added the 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 um It was 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 Um, it is removed from the first project board and added to the second project board as well At the moment a general contributor can't do 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 um remove labels I can remove that label And also remove it from um project boards like that. So the faculty member can do that for folks But yeah, so that is one of the automations we set up We can you read more about these automations? So we have created a new handbook page So I'm back in the training team handbook and the hell we use github We have automated workflows and this list um, the three different workflows we currently have set up So we have add a content development checklist We have label and triant feedback issues and we also have self-assigned an issue All right. So we just looked at the content feedback commands let's say um let's say you go to a project that the content development And let's say you want to work on this lesson plan. So Use dual tone filters to change color effects lesson plan. All right. So this is in 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 Um contributors all they have to do is type assign In a new comment oops My screen is just a bit small. Here we go type a sign in a new comment press comment And then we need to let the workflow run in the background for five ten minutes, but just wait And hopefully this will add me as an assigning Richard work Did I spell it right? Assign All right, it's not happening Um, that's live live tv for you, I guess So let me check that let me also Will it automate the 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. Uh-huh um, 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 um Let me open that up over here um So you see there are two 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 Um, but if you click on the title that will also take you to the issue itself And you'll see at the bottom here Ta-da, okay. So I assigned myself and then there was a new comment Hi Beats on events. Thank you for your interest in this issue If you have any questions, do not hesitate to ask them in our training slack channel Thank you for contributing. So that's a bit of a nice welcome message from github.com Now let's say for example, this issue was already assigned to me And but this different contributor over here Also tried doing the self assigned to themself So you see that was my faculty account that assigned that I'm back in my non-faculty accounts and let me try doing a sign Let's see what happens So again, it might take about five seconds There we go. Okay, it is Hi Nico Nico Beats on this issue is already assigned to be some of us A faculty administrator can also add you to the list of assigned needs or swap you with the current assigned need 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 it assigns 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 the 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 going to clear that out All right And then one final workflow. I wanted to show Um, so coming back to automated workflows We just looked at label and triage feedback issues self-assigning issue We also have one set up add 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 We have a content development issue for general contributors and we have one for training team faculty members um Now the general contributor they their issues go through a topic vetting process And the ones that's been vetted you're given instructions to copy and paste a content creation checklist into your issue um But for faculty who we have some faculty members who create One or two pieces of content every week Going to copy going and copy and 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 details of content type content title topic description, etc, etc Learning objectives, etc, etc. And then we have finally automation code So similar to how we triage feedback Under these comments types two slashes Followed by the content type tutorial online workshop lesson plan or course Once submitted that code will add a new comment to the issue with the relevant development checklist So let's let's say this was a lesson plan lesson plan um What the faculty needs to do is type slash slash lesson plan And then submit the new issue and a few different things happen here so Let's go Oh, 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 been 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 have any questions or things you want me to demonstrate again type in the zoom chat As we wrap up I'll just briefly show We have a page here That documents all the different github labels um Now labels are added here to an issue Until now, for example, when we 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 seven or eight or nine labels Which is quite confusing actually So what we've done recently is we've taken a lot of these labels and turned them into Custom fields. So what does that mean? So if you're content developer Again, this is um specific to faculty So the general contributor you'll need a faculty to set the custom fields for you The goal is to have automation for this as well, but it's not quite built yet So hopefully down the line we'll 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 six more Clicking on this shows the different custom fields you can apply to this issue in that project So if you have been a content developer with the training team since Two 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 up to review set so we can leave it as is Content type so this is a lesson plan topic this will be Let's say it's about the training team Main 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 version with most recent update. So this isn't applicable. So we'll leave that as is So by setting all these as custom fields We haven't we didn't need to set any labels on this Now they're waiting triage because i'm a faculty member the waiting triage means this issue is still waiting for custom fields It's waiting to be added to the right project and it's waiting for an assignee and the 24 custom field So if I assign the issue to myself I've set the different custom fields. 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 were we able to reduce the labels in the training team repo But we've also made the interface a lot less Platy Because until now we would have had like eight or nine labels on each of these issues. We just made it too complicated to look at um 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 um, but if you're interested to know what our labels are Used for then we have a handbook page here that lists the 27 labels used in the training team All right, so we went through a lot today. I gave an overview of how we use the github project boards to manage training team things um, 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 Um, 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 teams github repository Um, that was a lot of information. Are there any questions or comments about that or even Maybe you want me to show something again? Um Does anybody have any comment? Um 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 Um, yep, and john you said you wanted to see what's behind the curtain um Did that give you a good idea of what's behind the curtain? now um for the recording thing Um Courtney you say you haven't used workflows yet, but it seems pretty straightforward great um For example that selfish sign workflow. We still have to incorporate that into our onboarding program. It's not really No, like we're not notifying our new users yet about it because it's brand new And I've sort of been testing it for a while But now that we know it works. I think we can incorporate into our onboarding So all our new contributors know they can sell for sign issues to themselves Um Eagle the project flow is new to you. Um, I'm glad you learned something new Um tracy you learned a lot about the new updates laura. You're not scared as much. That's good news Um And laura, thank you for simplifying the labeling. 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 um Where do these automations live? Um, so if some if there's a developer out there who wants to help us build out these final bits of automation Um, you're more than welcome to join us. I would love to work with you Our 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 there's a file called incomplete workflows because there are still things that need to be created And if you run a workflow and you're like, uh, has it happened yet? Has it has it worked? Um, you can click on the actions tab here next to projects if you click on actions This keeps a record of all the automated workflows that ran in the background Um, so something doesn't look like it's working Developers will go to the actions tab 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 Um, so if there's ever a bug we can go in and debug it and fix things Um, 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 dot workers learn menu is created? make Are you talking about this menu dot make dot work? Are you talking about the the menu on this web on this website eagle on make WordPress? So let's go to This page We're training This is to make dot workers a little training This tab is made dot workers at all okay We're out time. So I'll continue this and zoom to answer your question eagle for the other folk Thank you for joining us and if you have any questions you can find me in the wordpress slack instance So feel free to reach out to me there and I'd be happy to answer questions even after this session is over Um eagle i'll be here for a couple more minutes I can pause the recording and we can go through your question together then All right, but thank you everybody for joining and I look forward to seeing you in another online workshop in the future Have a good day