-
Notifications
You must be signed in to change notification settings - Fork 64.1k
Tolong saya #41108
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
Tolong saya #41108
Conversation
Add a security policy document outlining supported versions and vulnerability reporting.
Bumps the npm_and_yarn group with 1 update in the / directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 6.3.6 to 6.4.1 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/[email protected]/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 6.4.1 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
…m_and_yarn-7372c7abf2 Bump vite from 6.3.6 to 6.4.1 in the npm_and_yarn group across 1 directory
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. This pull request contains code changes, so we will not generate a table of review links. 🤖 This comment is automatically generated. |
|
👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:
You'll need to revert all of the files you changed that match that list using GitHub Desktop or The complete list of files we can't accept are:
We also can't accept contributions to files in the content directory with frontmatter |
|
Saya tidak tahu apa apa, semua data pribadi saya hilang. Bisakah bantu saya. |
|
Re ever
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: github-actions[bot] ***@***.***>
Sent: Monday, November 3, 2025 6:41:30 PM
To: github/docs ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [github/docs] Tolong saya (PR #41108)
[https://avatars.githubusercontent.com/in/15368?s=20&v=4]github-actions[bot] left a comment (github/docs#41108)<#41108 (comment)>
How to review these changes 👓
Thank you for your contribution. To review these changes, choose one of the following options:
* Spin up a codespace<https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace>
* Set up a local development environment<https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment#setting-up-your-local-environment>
A Hubber will need to deploy your changes internally to review.
Table of review links
Note: Please update the URL for your staging server or codespace.
This pull request contains code changes, so we will not generate a table of review links.
🤖 This comment is automatically generated<https://github.com/github/docs/blob/f10e9864b2a8aa67a4b8d2b3e5bf3e4171c67141/.github/workflows/review-comment.yml>.
—
Reply to this email directly, view it on GitHub<#41108 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5BPXN4PJ2UDOJE7STI6FWT327R2VAVCNFSM6AAAAACLBHOIMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBTGAZDCOJTGA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Saya tidak mengerti
Pada Sel, 4 Nov 2025, 06.55, George Clapps ***@***.***>
menulis:
… *grcspace311* left a comment (github/docs#41108)
<#41108 (comment)>
Re ever
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: github-actions[bot] ***@***.***>
Sent: Monday, November 3, 2025 6:41:30 PM
To: github/docs ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [github/docs] Tolong saya (PR #41108)
[
https://avatars.githubusercontent.com/in/15368?s=20&v=4]github-actions[bot]
left a comment (github/docs#41108)<
#41108 (comment)>
How to review these changes 👓
Thank you for your contribution. To review these changes, choose one of
the following options:
* Spin up a codespace<
https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace>
* Set up a local development environment<
https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/creating-a-local-environment#setting-up-your-local-environment>
A Hubber will need to deploy your changes internally to review.
Table of review links
Note: Please update the URL for your staging server or codespace.
This pull request contains code changes, so we will not generate a table
of review links.
🤖 This comment is automatically generated<
https://github.com/github/docs/blob/f10e9864b2a8aa67a4b8d2b3e5bf3e4171c67141/.github/workflows/review-comment.yml>.
—
Reply to this email directly, view it on GitHub<
#41108 (comment)>, or
unsubscribe<
https://github.com/notifications/unsubscribe-auth/A5BPXN4PJ2UDOJE7STI6FWT327R2VAVCNFSM6AAAAACLBHOIMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBTGAZDCOJTGA>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#41108 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BZK3BW4VCZRSGIEPFPWQJN3327TPPAVCNFSM6AAAAACLBHOIMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBTGA3DENRYHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: