Skip to content

Temporarily remove yank button from crate header #2795

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
merged 1 commit into from
Sep 19, 2020

Conversation

jtgeibel
Copy link
Member

Temporarily remove the yank button from the crate page until we find better placement for the button. The buttons added to the all versions page in #2623 remain.

I would like to merge this as a temporary fix to unblock deploying to production. I've opened #2794 to track adding this back.

r? @locks
cc @thiagoarrais

@thiagoarrais
Copy link
Contributor

I'm all for this. Haven't ever been 100% happy with this header button since I've introduced it.

@jtgeibel jtgeibel force-pushed the hide-yank-button-in-crate-header branch 2 times, most recently from 9536a5c to 0ff5281 Compare September 19, 2020 22:06
@jtgeibel jtgeibel force-pushed the hide-yank-button-in-crate-header branch from 0ff5281 to 8ace99a Compare September 19, 2020 22:23
@jtgeibel
Copy link
Member Author

I skipped the failing test and rebased on master so that I could deploy.

@bors r=thiagoarrais

@bors
Copy link
Contributor

bors commented Sep 19, 2020

📌 Commit 8ace99a has been approved by thiagoarrais

@bors
Copy link
Contributor

bors commented Sep 19, 2020

⌛ Testing commit 8ace99a with merge 6cb1279...

@bors
Copy link
Contributor

bors commented Sep 19, 2020

☀️ Test successful - checks-travis
Approved by: thiagoarrais
Pushing 6cb1279 to master...

@bors bors merged commit 6cb1279 into rust-lang:master Sep 19, 2020
@jtgeibel jtgeibel deleted the hide-yank-button-in-crate-header branch September 20, 2020 04:06
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.

5 participants