4 ms·

Great post. Very clear explanation of things. The semantic release tooling is so good, I've started using it on non-js projects. I'm using it to manage Terrafo

Great post. Very clear explanation of things. The semantic release tooling is so good, I've started using it on non-js projects. I'm using it to manage Terraform modules, base docker images, etc. Once you're doing that, might as well mix in Husky and commit-lint to manage your git hooks and commit messages too. There are comparable things elsewhere, but node is so ubiquitous in my tool chain already that this is the path of least resistance for me. And it works great!

derberg 7y ago
I wanted to also introduce PR title validation, so there is no mistake possible on merging and we follow convetional commits 100% but unfortunately GitHub Actions do not support fork-based workflow properly and those PR checks would be useless :(
- time0ut 7y ago
  Oh, that is unfortunate. Hopefully they fix that. For now, it might be worth writing a little bot that will flag PRs with noncompliant commit messages and titles.
- jakear 7y ago
  > GitHub Actions do not support fork-based workflow properly Could you elaborate on this?
  - derberg 7y ago
    Take a look on my blog post about it https://dev.to/derberg/github-actions-when-fascination-turns-into-disappointment-4d75 https://dev.to/derberg/github-actions-when-fascination-turns.... I already reported this to GitHub Actions team and seems they are working on that. For reference https://github.community/t5/GitHub-Actions/GitHub-Action-workflow-is-executed-for-a-PR-from-a-forked-repo/m-p/50654#M7914 https://github.community/t5/GitHub-Actions/GitHub-Action-wor...
    - jakear 7y ago
      Ah yes, fork. My mind read that as branch as we barely ever use forks (enterprise environment and all) Issue comment-triggered Actions have a write-access GITHUB_TOKEN, unless I’m mistaken. You could implement the /ok-to-test flow with that. (I’m working on converting some of VSCode’s triage automation to Actions, for reference)
      - derberg 7y ago
        Guy from GitHub suggested the same, but how would you really see such workflow in action? all I have in mind seems so complicated that easier would be to write and host dedicated bot really. Supporting PR on Issue level sounds strange
derberg 7y ago
I was wondering how do you use semantic-release tooling in non-js. Do you use ".releaserc" file for config and then on CI execute with npx, to have pure repo with no JS thingy? Or are you just using package.json normally? maybe hidden in ".github" ?
- time0ut 7y ago
  I just use a package.json in the repo root as it doesn't really bother me. It very rarely changes so I pretty much forget its there.

derberg 7y ago

I wanted to also introduce PR title validation, so there is no mistake possible on merging and we follow convetional commits 100% but unfortunately GitHub Actions do not support fork-based workflow properly and those PR checks would be useless :(

time0ut 7y ago
Oh, that is unfortunate. Hopefully they fix that. For now, it might be worth writing a little bot that will flag PRs with noncompliant commit messages and titles.
jakear 7y ago
> GitHub Actions do not support fork-based workflow properly Could you elaborate on this?
- derberg 7y ago
  Take a look on my blog post about it https://dev.to/derberg/github-actions-when-fascination-turns-into-disappointment-4d75 https://dev.to/derberg/github-actions-when-fascination-turns.... I already reported this to GitHub Actions team and seems they are working on that. For reference https://github.community/t5/GitHub-Actions/GitHub-Action-workflow-is-executed-for-a-PR-from-a-forked-repo/m-p/50654#M7914 https://github.community/t5/GitHub-Actions/GitHub-Action-wor...
  - jakear 7y ago
    Ah yes, fork. My mind read that as branch as we barely ever use forks (enterprise environment and all) Issue comment-triggered Actions have a write-access GITHUB_TOKEN, unless I’m mistaken. You could implement the /ok-to-test flow with that. (I’m working on converting some of VSCode’s triage automation to Actions, for reference)
    - derberg 7y ago
      Guy from GitHub suggested the same, but how would you really see such workflow in action? all I have in mind seems so complicated that easier would be to write and host dedicated bot really. Supporting PR on Issue level sounds strange

derberg 7y ago

I was wondering how do you use semantic-release tooling in non-js. Do you use ".releaserc" file for config and then on CI execute with npx, to have pure repo with no JS thingy? Or are you just using package.json normally? maybe hidden in ".github" ?

time0ut 7y ago
I just use a package.json in the repo root as it doesn't really bother me. It very rarely changes so I pretty much forget its there.