Skip to content

Updates copier template and adds example template#15

Open
Matt-Carre wants to merge 6 commits into
mainfrom
update-and-copier
Open

Updates copier template and adds example template#15
Matt-Carre wants to merge 6 commits into
mainfrom
update-and-copier

Conversation

@Matt-Carre

Copy link
Copy Markdown
Collaborator

No description provided.

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (83d5447) to head (1ea82fa).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #15   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         6    +1     
  Lines           77        87   +10     
=========================================
+ Hits            77        87   +10     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Matt-Carre
Matt-Carre requested a review from TBThomas56 July 20, 2026 09:17
@Matt-Carre Matt-Carre changed the title Updates copier template and example templates to abide by new standards Updates copier template and adds example template Jul 20, 2026
@Matt-Carre Matt-Carre mentioned this pull request Jul 20, 2026

@JamesDoingStuff JamesDoingStuff left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work with the example template! Just a couple of things I have questions about

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably makes more sense to include in #16 instead

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deleted from this branch now, thank you, forgot about this one!

Comment thread src/copier_template/src/sample.env Outdated
Comment on lines +1 to +5
HOST=https://argo-workflows.workflows.diamond.ac.uk/
IMAGE=
TOKEN=
NAMESPACE=
AUTH=

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code edits this file, right? I worry that having this tracked by version control will end up with a token getting committed & pushed by accident at some point. Might need reworking slightly...

@Matt-Carre Matt-Carre Jul 22, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code doesn't edit that file, it edits the file just called .env (specifically, at the path 'src/.env'), this is used as an example so people know what the .env requires - can re-do this if that would be better?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah my mistake, sorry! Perhaps it'd be worth turning this into a readme explaining that, like how we do for the .env.local in the Workflows frontend?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good plan, thank you, and no problem!

Comment on lines +14 to +16
# from python_interface_to_workflows.prepare_to_submit import prepare_to_submit

# prepare_to_submit(True)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the commented out lines in the workflows for testing out submission? If so, do they need to remain in all the workflow templates or can they be removed?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are, but as this is being used as the template copy, I was thinking that we would want to include this to show how to submit workflows to users. Can delete if you'd like?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My preference would be to have a more centralised way of doing this if possible, rather than having this written in comments on every template file, but it's up to you. If you do leave it in, I'd consider adding another comment line explaining what it's for

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea - this functionality changes in the next branch, and its much more clear what happens there, so I think I'll just delete the comments in this PR

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

Successfully merging this pull request may close these issues.

2 participants