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

use tagged releases to pull core porting guides #544

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

Conversation

gotmax23
Copy link
Contributor

@felixfontein
Copy link
Collaborator

Looks good to me, except that this should have a changelog fragment (and that urls.py needs a module docstring).

I'm kind of glad that I never implemented that the porting guide is extracted from the ansible-core tarball (as the changelog yaml is). That would have made our life a lot more complicated.

@gotmax23 gotmax23 force-pushed the porting_guide_tagged branch from b60f03a to b3203f7 Compare August 1, 2023 22:35
As of ansible-community/community-topics#240,
the location of ansible documentation has changed.
This code allows figuring the applicable repo for a certain ansible-core
version.
@gotmax23 gotmax23 force-pushed the porting_guide_tagged branch from b3203f7 to 1569d16 Compare August 1, 2023 22:58
@gotmax23
Copy link
Contributor Author

I'd like to reconsider this now that the tagged releases are created automatically in ansible-documentation.

@felixfontein
Copy link
Collaborator

I guess we should revive this then :)

@felixfontein
Copy link
Collaborator

@gotmax23 do you want to continue with this, or should I rebase it and create a new PR?

@gotmax23
Copy link
Contributor Author

gotmax23 commented Dec 23, 2024 via email

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

Successfully merging this pull request may close these issues.

2 participants