Це відео не доступне.
Перепрошуємо.
GitHub branch rules (protect your git branches)
Вставка
- Опубліковано 7 чер 2022
- You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.
Ge started with Open Source in 10mins
• How to contribute to o...
LEARN MORE
JOIN our inclusive open source community EddieHub now for FREE ... eddiehub.org, also checkout my website and sign up to our community NEWSLETTER... eddiejaoude.io for my live stream + video schedule and community calls
Also join our community GitHub organisation by creating an issue with the type "invite me to the organisation" :)
I now have a 2nd UA-cam channel for short video clips of 60s or less, subscribe ...
/ eddiejaoudetv
SERVICES I USE AND RECOMMEND
Some of these might be affiliate links, no extra cost you to, but I get a little $ if you sign up, plus you might get a discount too
- Live streaming with Streamyard links.eddiejaou...
- Cloud hosting with Digital Ocean, you will get $100 FREE credit links.eddiejaou...
- Membership, Newsletters, CRM all in one with Kartra links.eddiejaou...
- Awesome backup platform, BackBlaze links.eddiejaou...
- Descript for video editing, audiograms and transcription links.eddiejaou...
- Riverside online recording studio for the best quality riverside.fm/?...
COMMUNITY SPONSORS
A BIG thank you to my GitHub Sponsors:
***
DailyDotDev github.com/dai...
Emma Wain github.com/ewainy
***
- Yona github.com/Yoname
- Santosh Yadav github.com/san...
FIND ME ON OTHER SOCIAL PLATFORMS
Don’t forget to support my channel by subscribing below, it’s free, and also share with your friends. Subscribe now!!
www.youtube.co...
Follow on other socials for behind the scenes footage, join discord to continue the conversation...
eddiejaoude.io
github.com/edd...
/ eddiejaoude
/ eddiejaoude
/ eddiejaoude
/ eddiejaoude
/ discord
github.com/Eddi...
Markdown crash course in 15mins!
Get a job by making your GitHub profile look professional, you can customise it by taking my FREE video and text course www.eddiejaoude.io/course-github-profile-landing
Awesome! Thank you for this. very helpful.
You're very welcome!
Thanks Eddie, this is a nice video (no surprise) 👍
Thank you Ahmad for the great feedback!
I wonder why you don't set a status check in the "Require branches to be up to date before merging" setting?! The description says: "The setting will not take effect unless at least one status check is enabled (see below)."
Thank You for the Information sir :)
Thank you for the great feedback Vinay!
Thank you.
You're welcome! thank you for the great feedback
Lets gooo!! great video Eddie!!
Thank you Sean!!
Very Good, thanks.
Thank you for the great feedback!
I wish GitHub would allow different merge strategies per branch. For example: Squash feature branches into develop; but environment branches get "regular" merges. Any guidance on how to accomplish that? Seems to me that option is either on/off for the whole repo and whatever method you did most recent is the button state at the next merge.
yes unfortunately this is at a repo level not a branch level. I think the maintainers just need to be aware. You could have a GitHub Action that added a relevant comment depending on the destination branch, this would remind the person merging
Thanks for the video! At 3:06 when you metion about "Require status checks to pass before merging" how do you manage that check if you use jenkins for CI/CD instead of github actions ?
thank you for watching! If your Jenkins shows up as a check, then this will be included in the "required status checks"
How can i allow my pipeline to tag the main if prs are required by the rule? Can i give it permission without creating a pull request? The rule in general is absolutely useful, but the github action is the only exception.
is it possible to enable branch protection rules at the organisation level in Github so that all repositories part of that organisation inherit these rules for the applied branches. Right now its really a hassle to enable those same set of rules on a per repo basis for same set of branches.
I am not aware this is possible yet, but I am sure in the future there might be a way to do it at the organisation level
I don't understand fully what you speak about the branches option because I used it only once when I discover the basics on Git and it was in a basic level.
I will try to explain a bit more, git can have branches, but these branches can be protected on github so even if someone has permission to push to that branch, they need to follow more rules
@@eddiejaoude Okay
You look like that guy in Ex Machina
Lol yes 😂👍
Super weird... i just made a repo and i dont see a "Branches" option on the left hand side.
Oh strange, can you join us in the EddieHub Discord and you can share some links and screenshots
how do i add username or mail id associated with github which triggers a mail asking for approval when someone pushed code into main branch
click on watch the repo and you will get all notifications
6:13
this feature is not free?
yes it is free
It is not free for private repositories.
@@mayankhb ouch!