You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a bunch of repos under the rust-lang organization that are published as crates.io crates. Maintainers of such crates often go to Zulip to ask (infra, or other) people for publishing the crate.
It would be great if we could add GitHub CI workflow pipelines to said repositories to automate this process. The simplest way to do that is to crate a workflow that either publishes when a tag is pushed, or manually (through workflow_dispatch).
For now, we'll need an infra admin to manually configure a crates.io token for each repository.
Some repositories that I have encountered so far that had asked for a release recently:
We have a bunch of repos under the
rust-lang
organization that are published as crates.io crates. Maintainers of such crates often go to Zulip to ask (infra, or other) people for publishing the crate.It would be great if we could add GitHub CI workflow pipelines to said repositories to automate this process. The simplest way to do that is to crate a workflow that either publishes when a tag is pushed, or manually (through workflow_dispatch).
For now, we'll need an infra admin to manually configure a crates.io token for each repository.
Some repositories that I have encountered so far that had asked for a release recently:
release-plz
for automatic releases. compiler-builtins#643)The text was updated successfully, but these errors were encountered: