Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

distinguish between upstream and origin #50

Open
gedw99 opened this issue Nov 10, 2022 · 0 comments
Open

distinguish between upstream and origin #50

gedw99 opened this issue Nov 10, 2022 · 0 comments

Comments

@gedw99
Copy link

gedw99 commented Nov 10, 2022

This tool is nice. I have a similar one written as makefiles but would be into the idea of working on this.

my use case is that often on big multi repos i need to pull in upstreams and origins and also have them at different branches.

for example very often i will want to have both the origin and the upstream pulled, because i am a maintainer and have my own fork.
i use a generic system for this where i call the folder "gitty", and then the origin and upstream and pulled into.

By having a .env file, the system can see what ssh user i am and when i pull the the upstream, it will also pull the origin ( which is my fork.

also because it has al this info it can automatically add the correct git configs.

then i also gen the VSCode workspace for it correctly so that golang debugging with delve in viscose works properly.

This makes it very easy to have many branches of the same code in front of me.

the other cool thing is that you can also gen the go.work files, because there is enough info in the .env or config.
https://go.dev/doc/tutorial/workspaces
its important because you want to put in overrides into your galang project, but NOT mess up others working on the same code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant