Feature request: set attributes in a file which GitHub would use when rendering AsciiDoc
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.
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.