Skip to content

Conversation

@kroenlein
Copy link
Collaborator

GEMD Python PR

Description

This PR moves to using the common-gh-actions repo instead of locally defined actions.

PR Type:

  • Breaking change (fix or feature that would cause existing functionality to change)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Maintenance (non-breaking change to assist developers)

Adherence to team decisions

  • I have added tests for 100% coverage
  • I have written Numpy-style docstrings for every method and class.
  • I have communicated the downstream consequences of the PR to others.
  • I have bumped the version in __version__.py

@kroenlein
Copy link
Collaborator Author

Reverted update to deploy.yml as per CitrineInformatics/common-gh-actions#3

Comment on lines 13 to 17
# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
concurrency:
group: "pages"
cancel-in-progress: false
Copy link
Contributor

Choose a reason for hiding this comment

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

I found that this stanza actually causes the workflow to be cancelled, since it also exists in the common actions version. I think best is to leave it in the common actions workflow, so each caller doesn't have to worry about it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sounds reasonable. 👍

Copy link
Contributor

@anoto-moniz anoto-moniz left a comment

Choose a reason for hiding this comment

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

Just that one issue. Other than that, looks good!

@kroenlein kroenlein merged commit 26c6be8 into main May 15, 2024
@kroenlein kroenlein deleted the maintain/centralize-actions branch May 15, 2024 18:35
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.

3 participants