Uh oh!
There was an error while loading. Please reload this page.
Improve description of function migration - #12743
Merged
Merged
Conversation
alambforce-pushed
the
alamb/improve_description
branch
from
October 3, 2024 17:01
28593da to
6b37c69Compare26 tasks
alambforce-pushed
the
alamb/improve_description
branch
from
October 3, 2024 17:05
6b37c69 to
de2f528Comparealamb
marked this pull request as ready for review
October 4, 2024 11:11
comphead
approved these changes
Oct 9, 2024
alamb
commented
Oct 9, 2024
ContributorAuthor
Thank you for the review @comphead 🙏 |
Omega359
commented
Oct 9, 2024
Contributor
lgtm as well |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Part of #12740
Rationale for this change
@Omega359 has created the basic framework for automatically generating content in #12668
There will be a period of transition as we migrate the existing content to the new code style
We should make it it very clear what is happening during this transition period
What changes are included in this PR?
Add heading and links to the different function pages explaining the transition
Here is an example:
Are these changes tested?
Are there any user-facing changes?
Improved docs, no functional changes