Skip to content
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

Document the requirement to push releases #2109

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

axelson
Copy link
Contributor

@axelson axelson commented Apr 6, 2025

Currently there isn't any documentation about the requirement to push releases/tags to the source_url to get links to specific versions of the code. So this PR adds this documentation.

I couldn't find a general spot where source_url is talked about so I added an admonition near where it is first introduced.

Background: recently (in PostHog/posthog-elixir#14 (comment)) I was asked where the requirement for pushing git tags comes from. I wasn't able to find any official documentation (here or in https://hexdocs.pm/elixir/writing-documentation.html) so I have created this PR.

Here's what it looks like when I build the documentation locally:
Screenshot 2025-04-06 07-48-40@2x

Currently there isn't any documentation about the requirement to push
releases/tags to the `source_url` to get links to specific versions of
the code. So this PR adds this documentation.

I couldn't find a general spot where `source_url` is talked about so I
added an admonition near where it is first introduced.
Copy link

github-actions bot commented Apr 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants