We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently the docs generate links based on a specific version/tag of the source, instead of master.
master
For example https://hexdocs.pm/hound/Hound.Helpers.Element.html#inner_text/1 links to https://github.com/HashNuke/hound/blob/1.0.4/lib/hound/helpers/element.ex#L31
The problem with that is, the recent releases either aren't tagged, or are tagged with vx.x.x instead of just x.x.x.
vx.x.x
x.x.x
One solution would be to remove source_ref: "#{@version}" in mix.exs and make another release.
source_ref: "#{@version}"
Another solution would be to add the missing tags and make adding them part of the release process.
I'd be happy to do it the latter way myself, but it would require push permissions to this repo, it might be easier if one of the maintainers does it.
The text was updated successfully, but these errors were encountered:
Thanks for catching this. This should now be fixed for the latest release.
Sorry, something went wrong.
No branches or pull requests
Currently the docs generate links based on a specific version/tag of the source, instead of
master
.For example https://hexdocs.pm/hound/Hound.Helpers.Element.html#inner_text/1 links to https://github.com/HashNuke/hound/blob/1.0.4/lib/hound/helpers/element.ex#L31
The problem with that is, the recent releases either aren't tagged, or are tagged with
vx.x.x
instead of justx.x.x
.One solution would be to remove
source_ref: "#{@version}"
in mix.exs and make another release.Another solution would be to add the missing tags and make adding them part of the release process.
I'd be happy to do it the latter way myself, but it would require push permissions to this repo, it might be easier if one of the maintainers does it.
The text was updated successfully, but these errors were encountered: