fix: parse gitlab pipeline status to their GitHub equivalent #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
ashearin
force-pushed
the
gitlab-conclusion-fields
branch
from
eb3f853 to
39f5ea3
Compare
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
ashearin
had a problem deploying
to
integration-test
GitHub Actions
Failure
ashearin
force-pushed
the
gitlab-conclusion-fields
branch
from
c849068 to
c28bf22
Compare
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
ashearin
force-pushed
the
gitlab-conclusion-fields
branch
from
c28bf22 to
eb6ffe5
Compare
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
ashearin
temporarily deployed
to
integration-test
GitHub Actions
Inactive
Signed-off-by: Allen Shearin <[email protected]>
* Trust pinned GitHub download URLs Trust files that are downloaded from `raw.githubusercontent.com` where the file's ref is a Git SHA and therefore immutable. Resolves ossf#3339. Signed-off-by: martincostello <[email protected]> * Move logic to function - Add `hasUnpinnedURLs` function. - Add test cases for different URLs. Signed-off-by: martincostello <[email protected]> * Fix formatting Appease the linter. Signed-off-by: martincostello <[email protected]> * Suppress lint warnings Suppress warning on three long URLs. Signed-off-by: martincostello <[email protected]> * Address peer review Address peer review feedback. Signed-off-by: martincostello <[email protected]> * Fix lint warning Fix lint warning. Signed-off-by: martincostello <[email protected]> Signed-off-by: Allen Shearin <[email protected]>
Bumps [github.com/google/go-containerregistry](https://github.com/google/go-containerregistry) from 0.16.1 to 0.17.0. - [Release notes](https://github.com/google/go-containerregistry/releases) - [Changelog](https://github.com/google/go-containerregistry/blob/main/.goreleaser.yml) - [Commits](google/go-containerregistry@v0.16.1...v0.17.0) --- updated-dependencies: - dependency-name: github.com/google/go-containerregistry dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: Allen Shearin <[email protected]>
Signed-off-by: Allen Shearin <[email protected]>
ashearin
force-pushed
the
gitlab-conclusion-fields
branch
from
d04c9a3 to
7632aa9
Compare
ashearin
had a problem deploying
to
integration-test
GitHub Actions
Failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note(In particular, describe what changes users might need to make in their
application as a result of this pull request.)