Hot answers tagged

24 votes

Pull request merge process requiring rebase after every commit merged into master?

The core issue here is that your CI process takes hours. Everything else is standard good practice as far as many companies/developers are concerned. The reason to always expect a feature branch to be ...
Flater's user avatar
  • 48.7k
15 votes
Accepted

Etiquette of mentioning issues/PRs from other projects (backlinks)

I don't understand the equivalence between linking issues (even across projects) and "me too" messages. They are not the same at all. We can continue to assume large project godzilla which ...
Thomas Owens's user avatar
  • 82.3k
4 votes

How to automate version bumping, when version bumping involves changes in source code and a git tag?

Am I trying to implement a bad strategy here? If the strategy works for you, then it is not a bad strategy. On the other hand, changing the same line of __init__.py in every feature branch is a ...
Bart van Ingen Schenau's user avatar
3 votes

Pull request merge process requiring rebase after every commit merged into master?

The specific setting in github is whether or not branches are required to be up to date with main in order to merge to main. You can turn that off. Your current build process presumably requires at ...
Steve Jessop's user avatar
  • 5,101
3 votes
Accepted

Advice on Developing Shared Public Libraries in Visual Studio

I think you've positioned yourself inbetween two workable scenarios and the hassle you're dealing with now is the result of not sticking to one scenario in particular. You're using Nuget packages, ...
Flater's user avatar
  • 48.7k
3 votes

Should frontend and backend be on separate GitHub repos?

You may want to check monorepo(single repository) or separate repositories. When you have Monorepo: It is easy to keep your backend and frontend versions the same. Have atomic commits. Centralized CI/...
Kaan Ateşel's user avatar
2 votes

What are the best practices for Github Actions when it comes to splitting a wofklow into multiple jobs?

What are the best practices and the rational behind them? I am generally guided by two principals: MTTF - Mean Time To Feedback. DRY - Don't repeat yourself. I won't spend much time on MTTF since ...
DavidT's user avatar
  • 3,288
2 votes

Using GitHub repository as API

Using a repo probably violates their terms of service and in any case would be fragile. They have GitHub Pages, which is probably going to be free at your scale. I would suggest looking into that or ...
jmoreno's user avatar
  • 10.8k
2 votes

Is there any advantage of pushing branches to GitHub without an associated PR?

I feel like I should first address some apparent premises that this kind of question is based on. Being able to share code to a remote repository that multiple people have access to (read-write or ...
Guildenstern's user avatar
2 votes

Multiple SSH keys for different organizations

Things have changed quite a bit since this answer. There is now a path to do exactly what OP is requesting via fine grained Personal Access Tokens. The fine grained permission ability is (currently) ...
BobTuckerman's user avatar
1 vote

Migrating from Bitbucket to Github and using Git Flow

That does sound like an awful lot of repositories, and perhaps some of them should be combined if synchronization is key. With regard to keeping repos synced with one another, perhaps git submodules ...
user1059469's user avatar
1 vote

Should a github maintainer rewrite author's in pull requests?

I’m not a big-time OSS developer but I’ve never seen this practice. It’s also completely unnecessary. Some Git workflows incorporate patches from email, which means that a new commit will be made ...
Guildenstern's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible