Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/gitstar-oc/skills-test-with-actions

My clone repository
https://github.com/gitstar-oc/skills-test-with-actions

Last synced: 17 days ago
JSON representation

My clone repository

Host: GitHub
URL: https://github.com/gitstar-oc/skills-test-with-actions
Owner: Gitstar-OC
License: mit
Created: 2024-11-30T10:17:58.000Z (23 days ago)
Default Branch: main
Last Pushed: 2024-11-30T11:16:01.000Z (23 days ago)
Last Synced: 2024-11-30T11:22:28.920Z (23 days ago)
Size: 30.3 KB
Stars: 0
Watchers: 1
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

README

# Test with Actions

_Create workflows that enable you to use Continuous Integration (CI) for your projects._

## Step 4: Add branch protections

_Great job uploading test reports! :partying_face:_

Take a look at the merge box, you'll notice you can merge this even though the review process hasn't been met.

Protected branches ensure that collaborators on your repository cannot make irrevocable changes to branches. Enabling protected branches also allows you to enable other optional checks and requirements, like required status checks and required reviews.

### :keyboard: Activity: Add branch protections

1. Go to **Branches** settings. You can navigate to that page manually by selecting the right-most tab in the top of the repository called **Settings** and then clicking **Branches**.
1. Click **Add classic branch protection rule** under "Branch protection rules".
1. Type `main` in **Branch name pattern**.
1. Check **Require a pull request before merging**.
1. Uncheck **Require approvals**.
1. Check **Require status checks to pass before merging**.
1. Check all build and test jobs that you'd like to see in the newly visible gray box.
1. Click **Create**.
1. _Once you turn on branch protection, Actions can no longer push directly to the `main` branch. Wait about 20 seconds and then go to the `ci` branch. [GitHub Actions](https://docs.github.com/actions) will automatically update to the next step on the `ci` branch. You'll need to follow instructions on this branch._

---

Get help: [Post in our discussion board](https://github.com/orgs/skills/discussions/categories/test-with-actions) • [Review the GitHub status page](https://www.githubstatus.com/)