Fedor Korotkov

I think something like that should work: ```python # .cirrus.star load("cirrus", "env") def main(): return { "env": { "GCP_CREDENTIALS_CONTENT": "ENCRYPTED[{}]".format(branchSpecificCredentialsName()) }, } def branchSpecificCredentialsName(): if env.get("CIRRUS_BRANCH") == "main": return "qwerty123"...

Interesting! Will keep an eye on @seriesci! Thanks for sharing! I was thinking about scoping metrics by build (aka SHA). That's why there is `merge_strategy` to merge metrics of the...

How GitHub is handling PR refs is a bit weird but dictated by supporting the fork-based workflow. If a PR is created from a fork then the `pull/*` will still...

To clarify, if you are not forking the repository, then something like this will work for you: ```yaml task: clone_script: | git clone --recursive --branch=$CIRRUS_BRANCH https://x-access-token:${CIRRUS_REPO_CLONE_TOKEN}@github.com/${CIRRUS_REPO_FULL_NAME}.git $CIRRUS_WORKING_DIR git reset --hard...

Closing this since we can't change the behaviour because of PRs from forks but there is a workaround if you sure there will be no such PRs.

@RDIL agreed. Updated the original comment.

@waghanza case is a bit different then just a [matrix modification](https://cirrus-ci.org/guide/writing-tasks/#matrix-modification). Each task uses it's own Dockerfile generated from a template for each commit. But yeah, in the current world...

I think you can workaround the issue with existing functionality. Output of the Starlark script is appended to the YAML config and only then evaluated. That allows to override some...

[Our parser is written in Go](https://github.com/cirruslabs/cirrus-cli/tree/master/pkg/parser) so it's not runner related and should work regardless. 👌 Agreed on extra `|` for accuracy. BTW you'll nee quotes. I've just added an...

Then I wonder of `CIRRUS_TASK_NAME` is available to boolevator. 🤔 Assigned to @edigaryev for further investigation.