Skip to content

Conversation

felicitymay
Copy link
Contributor

@felicitymay felicitymay commented Jun 1, 2023

Why:

Closes: #20784

This update is intended to clarify the behavior of the UI if the user is not the owner of an organization.

The note has turned out a little longer than I'd hoped. Feel free to tell me that this would be better as an additional step instead.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Add a note to clarify that for repositories in an organization, only an organization owner can see a link to accept the agreement.

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

This update is intended to clarify the behavior of the UI if the user is not the owner of an organization.
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jun 1, 2023
@felicitymay felicitymay added content This issue or pull request belongs to the Docs Content team actions This issue or pull request should be reviewed by the docs actions team and removed triage Do not begin working on this issue until triaged by the team labels Jun 1, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 1, 2023

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
actions/creating-actions/publishing-actions-in-github-marketplace.md fpt
ghec
fpt
ghec

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

@felicitymay felicitymay marked this pull request as ready for review June 1, 2023 11:08
@felicitymay felicitymay added the waiting for review Issue/PR is waiting for a writer's review label Jun 1, 2023
lecoursen
lecoursen previously approved these changes Jun 1, 2023
…marketplace.md

Co-authored-by: Laura Coursen <lecoursen@github.com>
@felicitymay felicitymay added this pull request to the merge queue Jun 1, 2023
@felicitymay felicitymay added the ready to merge This pull request is ready to merge label Jun 1, 2023
Merged via the queue into main with commit ca109b0 Jun 1, 2023
@felicitymay felicitymay deleted the felicitymay-fix-20784 branch June 1, 2023 15:27
@github-actions
Copy link
Contributor

github-actions bot commented Jun 1, 2023

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Explain how someone can sign the GitHub Marketplace Developer Agreement
2 participants