-
Notifications
You must be signed in to change notification settings - Fork 177
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
Use AppVeyor artifact URLs in manuscript front-matter #263
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,7 +12,7 @@ _A DOI-citable version of this manuscript is available at <https://doi.org/DOI_H | |
<small><em> | ||
This manuscript | ||
{% if ci_source is defined -%} | ||
([permalink](https://{{ci_source.repo_owner}}.github.io/{{ci_source.repo_name}}/v/{{ci_source.commit}}/)) | ||
([permalink]({{ci_source.manuscript_url}})) | ||
{% endif -%} | ||
was automatically generated | ||
{% if ci_source is defined -%} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's not obvious to me which commit we should show in line 19 below for AppVeyor builds. The manuscript filename contains the triggering commit, but this link contains the merge commit for a pull request build. However, the triggering commit doesn't correspond to the I don't see a better option that what is already here. I do expect the difference between the filename and link could cause confusion. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes it is confusing, but I think it's important that the manuscript contains the commit that actually created 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.
Because
ci_source.manuscript_url
is created in a separate Manubot functionadd_manuscript_urls_to_ci_params
, should we also ensure thatci_source.manuscript_url
is defined here? Or only check forci_source.manuscript_url
?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.
I don't think
ci_params
will ever exist withoutmanuscript_url
with the current manubot software because:https://github.com/manubot/manubot/blob/1b885c614634d6e88565ebcf5052b6884132ab32/manubot/process/util.py#L193-L196
But it doesn't hurt to be safe and possibly some users will have an outdated
manubot
python package with this version ofcontent/00.front-matter.md
, so I added the extra check in b07d870