-
Notifications
You must be signed in to change notification settings - Fork 62.2k
∆ #12216
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
∆ #12216
Conversation
* trigger tests * Trigger new build * Trigger new build * Trigger new build * Trigger new build * Trigger new build * Trigger new build * Trigger build * Trigger build * Trigger build * Trigger build Co-authored-by: “jmarlena” <“jmarlena@github.com”>
repo sync
repo sync
…re check type (#22653) * feat: stub two reset scripts * refactor: split lint script into two separate files * fix: revert back to original lint script * refactor: use commander interface for linting translation files * Skip reset attempt when violation list is empty So that "execSync(`cat ${log}...`)" in line 64 is never executed. When there are no errors, the log file is not created, and unless it had been previously created by another process, the script will error out. Co-authored-by: Marcelo Jacobus <marcelo.jacobus@gmail.com>
repo sync
repo sync
repo sync
repo sync
After reviewing a few other doc pages, adjusted indentation accordingly and spaced the numbered list items for consistency.
repo sync
repo sync
repo sync
repo sync
repo sync
Adding clarification about EMU users being able to view public repositories on github.com
repo sync
repo sync
repo sync
repo sync
repo sync
repo sync
* Explain force push cautions * add a sentence * Explain necessity of force push * More accurate noun
repo sync
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. |
Thanks for your submission. It appears that you've created a pull request using one of our repository's branches. Since this is Thanks again! |
#993
Thank you for contributing to this project! You must fill out the information below before we can review this pull request. By explaining why you're making a change (or linking to a pull request) and what changes you've made, we can triage your pull request to the best possible team for review.
See our CONTRIBUTING.md for information how to contribute.
For changes to content in site policy, see the CONTRIBUTING guide in the site-policy repo.
We cannot accept changes to our translated content right now. See the types-of-contributions.md for more information.
Thanks again!
-->
Why:
Closes [issue link]
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):