-
This will help commenting on to the issue once opened and closed
like
Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and…
-
When the other files in .github directory changed, the sync action will failed:
```
Pushing synced data to target branch.
To https://github.com/xxx/yyyy
! [remote rejected] dev -> dev (refusing t…
-
Early October 2024 work has simplified `cubewrite()` enough to move its contents into `process()` & unify the top level workflow under a single function.
This is dependent on merging #114, #118 and…
-
Description
This workflow runs whenever a new issue or pull request is opened.
Greet User: It uses the actions-ecosystem/action-create-comment action to post a customized comment directly on the is…
-
https://github.com/pyiron/pyiron_workflow/blob/9e776adc3cbcfefcfaa9357205ffc3ecf0540133/pyiron_workflow/channels.py#L494-L509
Is this a feature? This makes graph execution non deterministic, does i…
-
## Context
The GitHub [workflow docs](https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow) state:
> In a public repository, scheduled workflows are automa…
-
Hi,
I am trying to execute Cactus on a set of custom newick+genome files (assembled similar to the example).
I am working on an HPC cluster with PBS PRO and not SLURM is there any way to execute the…
-
For GitHub actions which use reusable workflows the job name is `{job_parent_name} / {job_name}` which will cause our job name replication code to not match.
omus updated
2 months ago
-
When using the action, the `exit 1` thrown by the cache step bubbles up to the workflow and shows an error even if everything else succeeds.
Is there a way to prevent that error from bubbling, or a…
-
@galenlynch @yonibrowning plan to integrate the sniffer sensor into the bonsai workflow