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

Pin linux docker image instead of git #7847

Merged
merged 1 commit into from
May 6, 2024

Conversation

larsevj
Copy link
Collaborator

@larsevj larsevj commented May 6, 2024

Resolves #7841

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure tests pass locally (after every commit!)

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

@larsevj larsevj force-pushed the pin_linux_docker_image branch from c59c910 to bae2e4d Compare May 6, 2024 13:08
@larsevj larsevj changed the title Try pin linux docker image Pin linux docker image May 6, 2024
Copy link
Contributor

@yngve-sk yngve-sk left a comment

Choose a reason for hiding this comment

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

🔫

@larsevj larsevj added the release-notes:skip If there should be no mention of this in release notes label May 6, 2024
@larsevj larsevj changed the title Pin linux docker image Pin linux docker image instead of git May 6, 2024
@larsevj larsevj enabled auto-merge (rebase) May 6, 2024 13:14
@larsevj larsevj merged commit aa01aa9 into equinor:main May 6, 2024
38 checks passed
@larsevj larsevj deleted the pin_linux_docker_image branch May 6, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:skip If there should be no mention of this in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Workflows failing due to updated git
2 participants