Repository navigation
[docs] Add protected resources page - #4616
Merged
Merged
Conversation
3 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4616 +/- ##
==========================================
+ Coverage 74.35% 74.35% +0.01%
==========================================
Files 1027 1027
Lines 50178 50178
Branches 10848 10848
==========================================
+ Hits 37303 37304 +1
+ Misses 11884 11883 -1
Partials 991 991 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
byronkarlen
force-pushed
the
wbk/fix-protected-channel-descriptions
branch
from
October 13, 2026 20:17
b54d8a0 to
4e1429a
Compare
byronkarlen
marked this pull request as ready for review
October 13, 2026 20:22
|
Subscribed to pull request
Generated by CodeMention Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead. |
tchayen
approved these changes
Oct 13, 2026
|
✅ Thank you for adding the changelog entry! |
byronkarlen
added a commit
to expo/expo
that referenced
this pull request
Oct 13, 2026
# Why We don't yet have docs for protected channels and we should since the feature has fully shipped. #50308 added docs for the Release Manager role but it only briefly touches on protected channels. # How - Added a new "Protected resources" page (`docs/pages/eas/protected-resources.mdx`) under "Reference", after "Webhooks" in the EAS sidebar. Originally was going to add it under the "Expo accounts" section, but this seemed like a better home for it. - Linked to this new page in our roles/account-types section, and audit logs section - Will update eas-cli reference in expo/eas-cli#4616 # Test Plan <img width="1296" height="869" alt="image" src="https://github.com/user-attachments/assets/cb8e6e1e-0b67-4b0b-8359-d0de7348a5cd" /> <img width="1299" height="870" alt="image" src="https://github.com/user-attachments/assets/c38394d4-d3c3-4eab-a86a-8f3fc9d43746" /> # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a changeset and followed [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
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
2 participants
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.
Why
The
channel:protectandchannel:unprotectdescriptions say only admins can publish to a protected channel. Release Managers and Owners can too.How
Updated both command descriptions.
Test Plan
Ran
eas channel:protect --helpandeas channel:unprotect --helpand checked the new descriptions.