1

A changelog is handy as one will see what changes reside in a certain release. A couple of months ago one of my tools was not working anymore. By consulting the Changelog it was possible to find the issue quite fast. Examples: https://github.com/030/n3dr/blob/master/CHANGELOG.md https://github.com/030/dip/blob/master/CHANGELOG.md By creating the Changelog ...


1

If the running is aware of it's IP, you could run github action step which takes that as an input var to aws cli or Terraform to update the security group applied to the instance you're targetting, then delete the rule when the run is done.


1

I was only wrapping my PyPI secret token in one pair of curly brackets! Two are required, like ${{ secrets.nmdc_schema_pypi_token }}


1

Here is what I did, I create a Makefile that includes my own method of image creation, .PHONY: image clean image-release image: image-release image-release: cargo build --release buildah unshare ./image/distroless.sh release clean: cargo -v clean For this purpose the only thing that matters is the image created by ./image/distroless.sh matches ...


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