Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

dates: refresh infra/tooling date annotations to Aug 2025 #2557

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

Merged
jyn514 merged 1 commit into rust-lang:master from ali90h:date-sweep-2025-08-infra
Aug 28, 2025

Conversation

Copy link
Contributor

@ali90h ali90h commented Aug 28, 2025

Updated explicit date annotations to 2025-08

Addresses #2528.

Copy link
Collaborator

rustbot commented Aug 28, 2025

Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using r? rustc-dev-guide or r? <username>.

@rustbot rustbot added the S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content label Aug 28, 2025
Copy link
Contributor Author

ali90h commented Aug 28, 2025

r? rustc-dev-guide

Copy link
Member

jyn514 commented Aug 28, 2025

you don't need reviews for small stuff like this.

oh i see you're not in the org—@rust-lang/wg-rustc-dev-guide any objection to adding ali to the team so they can get merge rights?

ali90h reacted with heart emoji

@jyn514 jyn514 merged commit 384f5a1 into rust-lang:master Aug 28, 2025
1 check passed
@rustbot rustbot removed the S-waiting-on-review Status: this PR is waiting for a reviewer to verify its content label Aug 28, 2025
Copy link
Contributor Author

ali90h commented Aug 28, 2025

Thanks @jyn514 I am very happy about this.

Copy link
Member

@jyn514 I think we would want to see some sustained contributions before we move there... often it happens people contribute for a bit then leave, otherwise we will have lots of churn in team membership (where some members do not even respond to questions of if they want to continue being in the team). To be clear, this is not a blocking concern (I would not want to gatekeep), so maybe others can decide that the churn is not something to be concerned about. Also, we don't have a charter I know of (I should actually just ask/search how others were accepted into the team), and we probably must create one, to avoid the ad-hoc.

ali90h reacted with heart emoji

Copy link
Contributor Author

ali90h commented Aug 29, 2025

Thanks for the guidance and continued support. I’ll keep contributing and hope to live up to your expectations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /