-
Notifications
You must be signed in to change notification settings - Fork 96
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
check release repository urls are https and have .git extensions #201
Comments
Please consider addressing this soon to avoid pull request like this: ros/rosdistro#2990 |
What's the specific need for |
I forget, @dirk-thomas do you remember? I remember running into this problem before and for some reason the build farm needed the extension or maybe some conditional logic requires it to differentiate something. |
I believe that github is smart enough to to give you what you want, but |
I can't recall the case we had before but we need the |
Okay. I'm all for consistency—I just wasn't sure if there was something actually breaking due to it. I'm pretty sure the Clearpath repos are all over the map with respect to including the suffix or not. Rather than scold users until they get it right, I suggest a regex match -> transform -> confirmation prompt. Eg:
More of an implementation pain, but better end experience, especially for new users of Bloom. |
I opened #233 to address this. It does not do the more advanced parsing and recommendations that @mikepurvis suggested, but it will check for |
Also adding a rosdistro CI check: |
This is an example of where the |
Currently when users are prompted for the release repository url on the first release for a distro, they can put what ever they want. If it is github, then we should ensure it is https and .git extended. Other tools in the toolchain should be more robust to this, but I'll enforce it in bloom for consistency.
The text was updated successfully, but these errors were encountered: