|
Boris Galerkin posted:That would work but it would be a a mess to maintain, especially on like an iPad where I don't really have the time/want to wait for it to push to both remotes. I just want to push to GitHub and then have it be mirrored to bitbucket (and maybe gitlab, can't have too many backups right?) automagically and done off my device. lol GitLab CI/CD
|
#
¿
Jan 9, 2019 08:54
|
|
|
|
| # ¿ May 14, 2024 21:09 |
|
|
Don't fork it unless you'll be making forked changes. Best to just pull in the appropriate RELEASE or STABLE branch into your build pipeline.
|
|
#
¿
May 5, 2019 20:02
|
|
|
Ironically it takes some skill to keep history clean, but you usually only want a clean history on key branches if you make lots of mistakes and need to revert atomic changes quickly. Most teams just tag releases and revert to last known good release. Depends on what and how you deploy.
|
|
#
¿
Mar 10, 2020 04:26
|
|
|
Have you looked at Meltano?
|
|
#
¿
Aug 20, 2023 19:46
|
|