Document rust-lang/rust CI artifact naming conventions#48
Draft
jieyouxu wants to merge 1 commit into
Draft
Conversation
marcoieni
approved these changes
Jul 5, 2026
Member
|
We could also add some code check that entries within a directory follow some convention based on that directory. |
Member
Author
The existence of this predates my time, it's less of an actual convention and more of a "this is how things happened to be" AFAIK. We don't need to merge this now, we can see if there's a more deliberate organization then just move artifacts to a better structure if we come up with one. (In fact that's probably much better, so I'll mark this as draft.) EDIT: rust-lang/infra-team#286 |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
It is my understanding as well that
rustc/prefix for artifact name by convention means that it is used by rust-lang/rust CI. So actually document this to make it explicit.cf. #47 (review).