Fedor Korotkov

No updates so far. Since people prefer to host GitLab in most of the cases. This feature will follow after self-hosted Cirrus.

@sio wow! That's an elegant workaround! Thanks for sharing! Do you have a Twitter account? Would love to share the blog post and mention you from [@cirrus_labs Twitter account](https://twitter.com/cirrus_labs).

Hey @royger, Cirrus CI triggers builds on a particular webhook events that GitHub generates for a repository. It seems in case of public mirrors GitHub is not proactively monitors your...

URLs are per build so if you use `skip_if` for some tasks than the latest URL won't work as you described. At the moment there is no way to have...

We are not planning to add such links since it will break a contract that all artifacts from a link come from a single build.

Hey @abravalheri, Right now these two variable are available at task execution time but not at the configuration parsing/evaluation phase. The working directory part is tricky since Cirrus agent tries...

I'll update the docs a bit later today. If you are generating the whole task then you should know the instance type and therefore the platform. You can probably check...

I was thinking about having a function like this: ```python def use_deep_clone(task): # ... ``` Which will check for `"windows_container" in task` to determine/guess the OS and then do something...

I guess [this feature in Starlark configuration](https://github.com/cirruslabs/cirrus-cli/issues/398) can help you to define some of the environment variables globally. You can add `.cirrus.star` file with the following content: ```python load("cirrus", "env")...

@anarazel what do you mean by "branch specific secrets"? You want to be able to access value of an encrypted variable in Starlark by its name?