Git

Hello,

I have only ever used git in very very basic way: commit, branch, merge request, that's pretty much it.

I have a use case where I pull the repository locally, branch (let's call it branch1), write some code, test it, commit, then create a merge request to master branch.

The merge request takes some time to be approved. During that time I would like to add more edits on top of those I submitted in the merge request. What would be the correct steps here?

Our team has three seniors. We have 3 juniors and more coming up.

We want to have some set of organization in our git repos. I want the three of us to be required reviewers for the team repos, but we three should be able to merge pull requests for our codes without having to get it code reviewed by the other two.

I tried setting up a codeowners file in github with our team admin group as the codeowner, but it is making me unable to merge PRs for my code without the other two reviewing it. I can add our individual handles as code owners, but that would mean I would need to update every individual repo if we get a new admin or one of us goes away.

What is the best way to achieve what I’m looking for? Please advise.

Audio and transcript of a discussion of the goals and intent of the Git Patch Stack project.

This is an audio recording I made to try and start to more clearly formulate my thoughts and ideas around these different Git workflows. I would love to hear your thoughts and ideas around these workflows and this topic in general.

Hi everyone, I've been in communication with GitHub's support team for several weeks, but unfortunately, they haven't been able to resolve this problem. Therefore, I'm hoping someone here has a solution.

I'm currently facing an issue where I can't push LFS (Large File Storage) objects to any of my repositories. Once I add an LFS object, I lose the ability to push. Here's the error message I receive when attempting to push my code to an empty repository: Link to Error on Pastebin. It just infinitely asks for password and fails every time.

I see this so often, but I don't understand it. Some people just fork a huge amount of repos and never commit anything to them. What's the point? Are they trying to pad their profile for potential employers or what?

It just clutters your active repos. Personally, I just remove forks once my PR gets merged upstream. And I only fork when I'm ready to push a commit.

Is there something I'm missing?

Back in 2016 I finally moved from mercurial to a git-based tool for version controlling my home dir. I now have six repos. The link is to my first article on it. I use tagging on my blog so you can find the other vcsh articles from there. It makes switching machines super-simple and encourages me to write utilities to make my life easier.