-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
WIP: Change the way Azure Devops project #2301
Conversation
Should fix issue oxsecurity#2300
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we do the same with SYSYSTEM_COLLECTIONURI
?
I was searching, I've a doubt if we can create an Azure DevOps org with a white space.
Many company use space in the project or repo name, maybe it's better to sanatize all, just in case, don't you think so?
…________________________________
From: Kurt von Laven ***@***.***>
Sent: Monday, January 30, 2023 10:01:18 PM
To: oxsecurity/megalinter ***@***.***>
Cc: Etienne Deneuve ***@***.***>; Author ***@***.***>
Subject: Re: [oxsecurity/megalinter] WIP: Change the way Azure Devops project (PR #2301)
@Kurt-von-Laven commented on this pull request.
Should we do the same with SYSYSTEM_COLLECTIONURI?
—
Reply to this email directly, view it on GitHub<#2301 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHWVEPTI7BKQS3TOXZUUPDWVATZ5ANCNFSM6AAAAAAULO3HQU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
By definition, an URI does not need to be encoded / decoded , so if SYSTEM_COLLECTIONURI is a valid URI, it should not be necessary to manipulate it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the catch and thanks for the PR :)
The megalinter-runner job issue is not related to this PR, that's why I force its merge |
And thanks for megalinter and the merge ;)
…________________________________
From: Nicolas Vuillamy ***@***.***>
Sent: Monday, January 30, 2023 10:27:59 PM
To: oxsecurity/megalinter ***@***.***>
Cc: Etienne Deneuve ***@***.***>; Author ***@***.***>
Subject: Re: [oxsecurity/megalinter] WIP: Change the way Azure Devops project (PR #2301)
@nvuillam approved this pull request.
Thanks for the catch and thanks for the PR :)
—
Reply to this email directly, view it on GitHub<#2301 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHWVEMAFYX3CYAK6IN4AX3WVAW57ANCNFSM6AAAAAAULO3HQU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@EtienneDeneuve you're welcome :) Note: ghcr.io seems down, or in bad shape... so the build of beta is currently failing ... when it will be available I'll notify here :) |
Should fix issue #2300