Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow stack #97

Open
mbruns91 opened this issue Oct 18, 2023 · 2 comments
Open

Workflow stack #97

mbruns91 opened this issue Oct 18, 2023 · 2 comments
Assignees

Comments

@mbruns91
Copy link

In other repos where the CI is already migrated (e.g. ironflow, pyiron_module_template and pyiron_contrib), there are some more workflows:

  • daily.yml
  • dependabot-pr.yml
  • pr-labeled.yml
  • pr-target-opened.yml
  • weekly.yml

I've added them for structuretoolkit, too. Is it intended that all our repos shall have more or less the same CI stack?

Maybe this issue should be placed in pyiron/actions, so feel free to move it there.

@mbruns91 mbruns91 self-assigned this Oct 18, 2023
@liamhuber
Copy link
Member

My vision would be that all the repos have the same CI foundation (those Workflows used in the pyiron module template), but of course some repos may have their own additional Workflows. I also don't think we need to be dogmatic about it -- if there's a good reason for a repo to omit or modify a workflow, or should -- but barring a good reason, life will be easier if things are more alike.

@mbruns91
Copy link
Author

Okay, totally agree 👍

@mbruns91 mbruns91 reopened this Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants