-
Notifications
You must be signed in to change notification settings - Fork 4
Readme update to GitHub urls #231
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
base: master
Are you sure you want to change the base?
Conversation
bhcopeland
commented
Dec 19, 2025
|
We should update these too: |
|
@roxell good spot, yes I was going to do that in a separate PR. But happy also to bundle it all into this. This just gets the top level README update. |
|
lets do it all in this PR, please. |
docs/contributing.md
Outdated
|
|
||
| The tuxmake issue tracker is also on Gitlab: | ||
| <https://gitlab.com/Linaro/tuxmake/-/issues>. | ||
| <https://github.com/kernelci/tuxmake/-/issues>. |
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.
The link doesn't work, please remove -/, think that's enough to make the link to be valid.
This is true for all links with -/, happens on more places in the PR.
docs/container-about.md
Outdated
|
|
||
| The source and build procedure for the containers can be found at in the | ||
| [tuxmake gitlab repository](https://gitlab.com/Linaro/tuxmake). | ||
| [tuxmake gitlab repository](https://github.com/kernelci/tuxmake). |
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.
[tuxmake gitlab repository] change this to github too.
There is a few more places where it says gitlab that should also be changed to github.
Update repository and issue tracker URLs to github.com/kernelci, Update license link. Remove GitLab/CI cover badges and Remove [[TOC]] which is gitlab specific syntax. Signed-off-by: Ben Copeland <ben.copeland@linaro.org>
|
|
||
| ## Sending your contributions. | ||
|
|
||
| Contributions should be sent as merge requests on the GitLab repository. |
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.
... sent as pull requests on the GitHub repository.
|
|
||
| If that's too high of a barrier for you to send your patches, you can also send | ||
| them by email to the maintainers. However, we really prefer merge requests | ||
| because the GitLab Continuous Integration will run all the tests against your |
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.
GitHub