how to force push feature branches...not main branch.. if we force main branch, its blocking other branches also from force pushing. it should work for normal branches.. when we do squashing commits and pushing --force is required.
That’s great - thank you. But I have a question for a different scenario - how do you invite collaborators to the git project WITHOUT having them download the code in the Main? Say, I have sensitive code in the main that I do not want anyone to download and have a copy of but I would like to build on top of it?
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.
How do I make Git stop tracking Configuration files, in a way that configuration files should remain in the repository server so that if someone new clones the repo, they should get the file but changes done by that someone new should not be tracked or atleast should not be committed to git remote server ? Configuration files needs to be tracked and committed only once. How can we prevent/freeze future commit on Configuration Files ?
In ".gitignore" file add : config/ and then . in terminal in vs code git rm -r --cached config/ git commit -m "Remove configs from Git's index" this might work ..
Thanks for the video, I have a question, I am setting a private git server as the hosting server, am I be able to set the branch protection rules by using Git Bash? Is there any command for that?
Thank you for your video. I have a question regarding restrictions. Imagine that we have 2 branches (development and production). How can we set a restriction which will block any merge between these 2 branches? I do not want these branches to be merged together.
If you don't merge the development branch with the main, how are you going to add the developments to the main file and what is the purpose of having a development branch in that case?
simple sentence, awesome definition, Informative. tnx bro. love from Bangladesh
short, simple and upto the point.....awesome.
Glad you liked it!
Concise information. Thank you Leela.
very clear and straight to the point ty !
Excellent and to the point - very helpful thank you!! 🙌
Good point,thanks for sharing this.everyone must know this.
Very neat and crisp explanation... keep up the good work! ✨👍
This was very concise. Nicely done
Thank You ...Great Video
Very nice explanation, thanks 💯👌
it was very clear thanks a lot sir!
Thanks!
Informative & Concise ❤
how to force push feature branches...not main branch.. if we force main branch, its blocking other branches also from force pushing. it should work for normal branches.. when we do squashing commits and pushing --force is required.
Very helpful thank you so much .............
Thank you so much
Good explanation
That’s great - thank you.
But I have a question for a different scenario - how do you invite collaborators to the git project WITHOUT having them download the code in the Main?
Say, I have sensitive code in the main that I do not want anyone to download and have a copy of but I would like to build on top of it?
in all the videos i see, i also see your comment lol. it means that im having the same issue. did you solve it? any news?
@@ilirbajrami2902 haha unfortunately, I still haven’t solved that issue
Very good
What if there is a conflict bt main and other protected branch? Please tell
best explanation
Video was so nice one think i request you add subtitle
how i can't set that only one person can merge PR to Stage?
how to add collaborator in a specific branch?
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.
Can i use this without using git ?
How do I make Git stop tracking Configuration files, in a way that configuration files should remain in the repository server so that if someone new clones the repo, they should get the file but changes done by that someone new should not be tracked or atleast should not be committed to git remote server ? Configuration files needs to be tracked and committed only once. How can we prevent/freeze future commit on Configuration Files ?
In ".gitignore" file
add :
config/
and then . in terminal in vs code
git rm -r --cached config/
git commit -m "Remove configs from Git's index"
this might work ..
thanks, this helped
Great great video
this is good
Thanks for the video, I have a question, I am setting a private git server as the hosting server, am I be able to set the branch protection rules by using Git Bash? Is there any command for that?
I didnt worked on the private repo, need to check
Thank you for your video. I have a question regarding restrictions. Imagine that we have 2 branches (development and production). How can we set a restriction which will block any merge between these 2 branches? I do not want these branches to be merged together.
If you don't merge the development branch with the main, how are you going to add the developments to the main file and what is the purpose of having a development branch in that case?
Can you create video on git patch
Noted
this is showing in paid version for Private Repo, while this free for public repo
yeah
So this feature is paid for private repo? That was what I’m looking for. This is a difficult decision 😭
Finally, I found it .....
very nice