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

chore: run devtools::document() #1710

Merged
merged 1 commit into from
Feb 24, 2025
Merged

chore: run devtools::document() #1710

merged 1 commit into from
Feb 24, 2025

Conversation

szhorvat
Copy link
Member

@maelle Running devtools::document() gives me these changes. Does this look expected, and if yes, can we merge this PR so we won't keep having conflicts from re-documenting?

@szhorvat szhorvat requested a review from maelle February 21, 2025 16:35
Copy link
Contributor

aviator-app bot commented Feb 21, 2025

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

@maelle maelle merged commit b1b66a0 into main Feb 24, 2025
6 checks passed
@maelle maelle deleted the doc-update branch February 24, 2025 07:58
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