Skip to content

Feature request: set attributes in a file which GitHub would use when rendering AsciiDoc #1257

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

Open
tjquinno opened this issue Feb 13, 2019 · 7 comments

Comments

@tjquinno
Copy link

Our build process passes attribute assignments at runtime (equivalent to the asciidoctorj -a option) when rendering .adoc files for publication elsewhere, for example to pass the project's release string. We would like to be able to accomplish essentially the same thing when GitHub renders our AsciiDoc.

In its simplest form this feature might have GitHub look for a single file with a fixed name that would contain attribute assignments. If it finds that file, GitHub would apply the attribute assignments from that file as it renders any .adoc file in that directory.

In a slightly more advanced implementation, when rendering X.adoc GitHub could look for X.adoc-github-attrs (for example) in the same directory and apply those attribute settings. Perhaps .adoc-github-attrs would apply to any rendered .adoc file, in addition to its specific attrs file (if any), with a clear precedence defined if both files define the same attribute.

There might be better approaches or naming conventions, but with luck this conveys the essence of the feature we're looking for.

@igorsantos07
Copy link

This is exactly the reason why I got sad when I discovered includes render as just file links (#1095), and having this could partially solve one of the many uses for includes.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Nov 24, 2024
@tjquinno
Copy link
Author

I know it's been 5+ years. Any thoughts about providing this??

@github-actions github-actions bot removed the Stale label Nov 25, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Jan 25, 2025
@tjquinno
Copy link
Author

No reaction at all from the team??

@github-actions github-actions bot removed the Stale label Jan 27, 2025
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Mar 28, 2025
@igorsantos07
Copy link

No reaction at all from the team.

@github-actions github-actions bot removed the Stale label Mar 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@igorsantos07 @tjquinno and others