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
{{ message }}
Repository navigation
Commit d67ced7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ Use the table of contents icon <img alt="Table of contents icon" src="/contribut
14
14
15
15
**Start here:** Visit [docs.github.com/en/contributing](https://docs.github.com/en/contributing) for complete contributor onboarding and guidelines.
16
16
17
+
As noted in our contributor onboarding guidelines, if an issue already exists, please don't start work on it until it has been assigned a `help wanted` label.
18
+
17
19
For repository-specific setup, read the [README](../README.md) file. The official docs site also provides these helpful resources:
18
20
19
21
-[Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
console.log('Every linked issue has the help wanted label')
69
+
return
70
+
}
71
+
72
+
await github.rest.issues.createComment({
73
+
owner,
74
+
repo,
75
+
issue_number: pull_number,
76
+
body: "Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a `help wanted` label. We need to properly assess all issues before we can accept community contributions, and determine whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be. For now, we're going to close this pull request.",
text: ${{ toJSON(format('You opened {0} publicly in github/docs instead of the private repo. An internal confirmation issue was created.', github.event.issue.html_url || github.event.pull_request.html_url)) }}
echo "Slack user lookup outcome: ${SLACK_LOOKUP_OUTCOME:-not run}"
165
+
if [ -z "$SLACK_USER_ID" ]; then
166
+
echo "Slack DM skipped because no Slack user ID was resolved."
167
+
elif [ "$SLACK_DM_OK" = "true" ]; then
168
+
echo "Slack DM sent successfully (timestamp: ${SLACK_DM_TS:-unavailable})."
169
+
else
170
+
echo "Slack DM did not return success (step outcome: ${SLACK_DM_OUTCOME:-unknown})."
171
+
if [ -n "$SLACK_DM_RESPONSE" ]; then
172
+
printf '%s\n' "$SLACK_DM_RESPONSE" | jq -r 'if type == "object" and (.error | type) == "string" then "Slack API error: " + .error else "Slack API response did not include an error field." end'
SLACK_MESSAGE: <@${{ github.actor }}> opened https://github.com/github/docs/issues/${{ github.event.number || github.event.issue.number }} publicly on the github/docs repo instead of a private repo. They have been notified via a new issue in the private repo to confirm this was intentional.
SLACK_MESSAGE: ${{ format('{0} opened {1} publicly in github/docs instead of the private repo. An internal confirmation issue was created.', steps.slack_user.outputs.slack_mention, github.event.issue.html_url || github.event.pull_request.html_url) }}
echo "Slack channel notification sent successfully (timestamp: ${SLACK_CHANNEL_TS:-unavailable})."
203
+
else
204
+
echo "Slack channel notification did not return success (step outcome: ${SLACK_CHANNEL_OUTCOME:-unknown})."
205
+
if [ -n "$SLACK_CHANNEL_RESPONSE" ]; then
206
+
printf '%s\n' "$SLACK_CHANNEL_RESPONSE" | jq -r 'if type == "object" and (.error | type) == "string" then "Slack API error: " + .error else "Slack API response did not include an error field." end'
207
+
else
208
+
echo "Slack channel API response was unavailable."
Copy file name to clipboardExpand all lines: content/account-and-profile/how-tos/account-management/deleting-your-personal-account.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Deleting your personal account
3
-
intro: You can delete your personal account on {% data variables.location.product_location %} at any time.
3
+
intro: You can delete your personal account on {% data variables.location.product_location %} from your account settings.
4
4
redirect_from:
5
5
- /articles/deleting-a-user-account
6
6
- /articles/deleting-your-user-account
@@ -46,6 +46,14 @@ Before you delete your personal account, make a copy of all repositories, privat
46
46
> [!WARNING]
47
47
> Once your personal account has been deleted, {% ifversion fpt or ghec %}{% data variables.product.company_short %}{% elsif ghes %}an enterprise owner{% endif %} cannot restore your content.
48
48
49
+
{% ifversion fpt or ghec %}
50
+
51
+
If your account is flagged, suspended, or otherwise restricted, **Delete your account** may be unavailable, disabled, or direct you to {% data variables.contact.github_support %} instead of completing deletion. Contact {% data variables.contact.contact_support_page %} to request access to the normal self-service deletion flow.
52
+
53
+
{% data variables.contact.github_support %} does not delete your personal account on your behalf. Once access is restored, you must complete the steps below to delete your account.
54
+
55
+
{% endif %}
56
+
49
57
{% data reusables.user-settings.access_settings %}
50
58
{% data reusables.user-settings.account_settings %}
51
59
1. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your personal account:
Copy file name to clipboardExpand all lines: content/billing/how-tos/troubleshooting/locked-account.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,8 @@ category:
26
26
27
27
You can unlock and access your account by updating your account's payment method and resuming paid status. We do not ask you to pay for the time elapsed in locked mode.
28
28
29
+
A failed authorization hold when you try to sign up for {% data variables.product.prodname_copilot_short %} or increase a budget can also lock your personal account billing and block {% data variables.product.prodname_actions %} or other free-tier access. This can happen even if you plan to stay on {% data variables.product.prodname_free_user %}, have removed the payment method, or see no active {% data variables.product.prodname_copilot_short %} plan or balance in the "Billing and licensing" section under your account's settings page.
30
+
29
31
You can downgrade your user account or organization to {% data variables.product.prodname_free_team %} to continue with the same advanced features in public repositories. For more information, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/downgrade-plan).
30
32
31
33
## Unlocking an account's features due to a declined payment
@@ -40,8 +42,10 @@ If the new billing information is approved, we will immediately charge you for t
40
42
41
43
When initiating a subscription or trial, we verify the entered payment method using an authorization hold. If the hold is unsuccessful, the chosen subscription or trial will not activate.
42
44
43
-
If your account's advanced features are locked due to a failed authorization hold, you'll need to update your billing information to trigger a new authorization.
45
+
If you want to continue with the chosen subscription, update your billing information to trigger a new authorization.
44
46
45
47
{% data reusables.billing.manage-payment-info %}
46
48
47
49
If the new authorization is successful, the account will automatically unlock and you will be able to proceed with the chosen subscription.
50
+
51
+
If the "Billing and licensing" section under your account's settings page shows no active subscription, balance, or payment issue to resolve, contact {% data variables.contact.contact_support %} to request a review of the billing lock.
0 commit comments