-
Notifications
You must be signed in to change notification settings - Fork 37
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
Substitution of branch names #98
Substitution of branch names #98
Conversation
Do we need to update the foxy branch? |
I'm not sure why CI fails now, |
I think the conf.py is only used from the master branch, but the links could be updated in foxy etc |
And we have to merge the linked PRs first, otherwise the not-any-more-existing substitution will fail. |
But if there's a deployment between merging the linked PRs and this, there will be broken links on the page for a short amount of time, nicht wahr? |
No, the "new" method was already there before. Merging the linked PRs won't
break anything
Bence Magyar ***@***.***> schrieb am Di., 23. Mai 2023, 18:09:
… But if there's a deployment between merging the linked PRs and this, there
will be broken links on the page for a short amount of time, ja?
—
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZWCTFHCEOWQVCM5GJTZ43XHTOL3ANCNFSM6AAAAAAYKITTNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Ok boss
…On Tue, 23 May 2023, 17:24 Christoph Fröhlich, ***@***.***> wrote:
No, the "new" method was already there before. Merging the linked PRs won't
break anything
Bence Magyar ***@***.***> schrieb am Di., 23. Mai 2023, 18:09:
> But if there's a deployment between merging the linked PRs and this,
there
> will be broken links on the page for a short amount of time, ja?
>
> —
> Reply to this email directly, view it on GitHub
> <
#98 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAZWCTFHCEOWQVCM5GJTZ43XHTOL3ANCNFSM6AAAAAAYKITTNM
>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA24PYNM5M6K4JDYPXN5VODXHTQD7ANCNFSM6AAAAAAYKITTNM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
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.
Can be merged when CI is happy
If I'd know why it is failing 🤔 |
ros2_control_demos was published successfully with the latest changes. lets merge the PRs in the other two repos, then I'll try to fix the failing CI. maybe this is an artefact of the build script, which checks out the master branch instead of the one from the PR, where the missing requirement was not installed from. |
Branches merged |
@Mergifyio backport humble |
✅ Backports have been created
|
I realized that the extension used from #85 works only in the preamble but not within directives, i.e., refs/links etc.
I reverted that change and propose the usage of the already existing macro
expand_macros
connected to thesource-read
event of sphinx: The key{REPOS_FILE_BRANCH}
was already existing, and works now everywhere as far as I know.