See how custom Actions can be used to check pull requests before they are accepted.
- [Instructor] Pull requests, also known as PRs, … are used to facilitate conversation around code. … Typically, a PR is generated … when someone wants to merge code … from one repository branch into another. … But they are also widely used … when one developer has made an update … in a clone repository and wants to let … the original developer know about the change … in the hopes that they can merge … into the original repository. … The PR features on GitHub are great for this purpose, … because they allow the owner of the repo … to review the potential changes, make comments, … and if all goes well, merge the code … into the receiving repository. … However, managing pull requests can be tedious. … Fortunately, we can use GitHub Actions … to automate just about all of the steps needed … to accept and merge a pull request. … In this scenario, we'll develop a workflow … that approves and merges pull requests … based on the username associated with the account … that submitted the PR. …
- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Using environment variables
- Building custom actions
- Use cases for actions and workflows
Skill Level Beginner
1. Your first Action
2. Connecting Actions with Workflows
3. Using Actions
4. Building Custom Actions
5. Use Cases
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.