Open liemle3893 opened 4 years ago
Hi, thanks for this information. I'm in the process of adding support for GitHub Actions as well so let me combine these information so we can support the 3 CI's. By the way, what is this magic number 4b825dc642cb6eb9a060e54bf8d69288fbee4904
? Is this documented somewhere?
@flowerinthenight Here is the doc. https://git.wiki.kernel.org/index.php/Aliases
Try some things like:
$ printf '' | git hash-object -t tree --stdin
also work.
Nice. TIL something. Thank you.
Anyway, I just committed my changes to GitHub Actions. At the moment, the build allows the $COMMIT_RANGE variable to be overridable. You can try setting this variable in GitLab and build.sh will use that range instead.
If you have a GitLab yml file, you can do a PR, even though it's just wip, so I can add it and connect this repo to GitLab. That way, we can use your commit instead of just me copying your code. If you don't mind, that is.
I've just created a PR: https://github.com/flowerinthenight/golang-monorepo/pull/4. Please take a look at it.
Hi! Any updates? Did you resolve other "Need help" things? As I studied, this is the best monorepo template for golang.
No I haven't yet. No extra time at the moment.
Let's user edit ci file to correct their pipeline.
eg:
Where:
This way, I can flexible using Gitlab or Circle CI as my choice.
Note: This also solve the problem when repo only have 1 commit.