-
Notifications
You must be signed in to change notification settings - Fork 44
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
SUP-1759-resolve-a-default-pipeline #206
Merged
Merged
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
lizrabuya
requested review from
jradtilbrook,
mcncl and
james2791
as code owners
February 23, 2024 04:15
mcncl
approved these changes
Feb 26, 2024
yob
added a commit
that referenced
this pull request
Feb 28, 2024
In #206 gopkg.in/src-d/go-git.v4 was added as a dependency, which has led to a couple of GH security alerts. Reading the details on the two alerts, it seems like we're unlikely to be impacted. We're using it to parse git URLs and not clone repositories onto a filesystem, so we're not working with untrusted input. I thought I'd try upgrading the dependency to v5 anyway though. We'll be on the latest version which will help with keeping the project maintainable, and maybe the security alerts will go away as a side effect.
yob
added a commit
that referenced
this pull request
Feb 28, 2024
In #206 gopkg.in/src-d/go-git.v4 was added as a dependency, which has led to a couple of GH security alerts. Reading the details on the two alerts, it seems like we're unlikely to be impacted. We're using it to parse git URLs and not clone repositories onto a filesystem, so we're not working with untrusted input. I thought I'd try upgrading the dependency to v5 anyway though. We'll be on the latest version which will help with keeping the project maintainable, and maybe the security alerts will go away as a side effect.
yob
added a commit
that referenced
this pull request
Feb 28, 2024
In #206 gopkg.in/src-d/go-git.v4 was added as a dependency, which has led to a couple of GH security alerts. Reading the details on the two alerts, it seems like we're unlikely to be impacted. We're using it to parse git URLs and not clone repositories onto a filesystem, so we're not working with untrusted input. I thought I'd try upgrading the dependency to v5 anyway though. We'll be on the latest version which will help with keeping the project maintainable, and maybe the security alerts will go away as a side effect. I had to bump the default 1 min timeout on golint to get the linting step to pass. Looking at some recent builds golint was taking very close to 1min, so I guess this was enough to push it over? It only takes a few seconds on my laptop, maybe we need better/bigger CI instances?
mcncl
pushed a commit
that referenced
this pull request
Feb 28, 2024
In #206 gopkg.in/src-d/go-git.v4 was added as a dependency, which has led to a couple of GH security alerts. Reading the details on the two alerts, it seems like we're unlikely to be impacted. We're using it to parse git URLs and not clone repositories onto a filesystem, so we're not working with untrusted input. I thought I'd try upgrading the dependency to v5 anyway though. We'll be on the latest version which will help with keeping the project maintainable, and maybe the security alerts will go away as a side effect. I had to bump the default 1 min timeout on golint to get the linting step to pass. Looking at some recent builds golint was taking very close to 1min, so I guess this was enough to push it over? It only takes a few seconds on my laptop, maybe we need better/bigger CI instances?
yob
added a commit
that referenced
this pull request
Feb 28, 2024
In #206 gopkg.in/src-d/go-git.v4 was added as a dependency, which has led to a couple of GH security alerts. Reading the details on the two alerts, it seems like we're unlikely to be impacted. We're using it to parse git URLs and not clone repositories onto a filesystem, so we're not working with untrusted input. I thought I'd try upgrading the dependency to v5 anyway though. We'll be on the latest version which will help with keeping the project maintainable, and maybe the security alerts will go away as a side effect. I had to bump the default 1 min timeout on golint to get the linting step to pass. Looking at some recent builds golint was taking very close to 1min, so I guess this was enough to push it over? It only takes a few seconds on my laptop, maybe we need better/bigger CI instances?
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.
This PR implements a function that will retrieve the git repository URL from a given path and returns the pipelines that matches the repo url(s) from within the org that matched