Skip to content
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

Update point 2 of Creating your first workflow #1529

Closed
wants to merge 1 commit into from

Conversation

shreeya-sengupta
Copy link

@shreeya-sengupta shreeya-sengupta commented Nov 21, 2020

On reading point 2 of Creating your first workflow section it is not clear that the commit should not be done immediately on the same branch (point 2) and the user should go to point 3 before committing. Adding an extra line in point 2 to inculcate this clarity.

Why:

Improvement in the "Github Action - Quickstart" document, section "Creating your first workflow". To the best of my understanding issue need not be created for a document updation and only a PR request should suffice.

What's being changed:

image
On reading point 2 of Creating your first workflow section it is not clear that the commit should not be done immediately on the same branch (point 2) and the user should go to point 3 before committing. Adding an extra line in point 2 to inculcate this clarity.

Check off the following:

  • All of the tests are passing.
  • I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
  • For content changes, I have reviewed the localization checklist
  • For content changes, I have reviewed the Content style guide for GitHub Docs.

On reading point 2 of Creating your first workflow section it is not clear that the commit should not be done immediately on the same branch (point 2) and the user should go to point 3 before committing. Adding an extra line in point 2 to inculcate this clarity.
@welcome
Copy link

welcome bot commented Nov 21, 2020

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.

@janiceilene
Copy link
Contributor

@shreeya-sengupta Thanks so much for opening a PR! I'll get this triaged for review 🌟

@janiceilene janiceilene added 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 ecosystem This issue or pull request should be reviewed by the Docs Ecosystem team labels Nov 23, 2020
@github-actions
Copy link
Contributor

This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit.

@github-actions github-actions bot added the stale There is no recent activity on this issue or pull request label Nov 30, 2020
@shreeya-sengupta
Copy link
Author

@janiceilene : Hi, thanks for adding it to the docs team reviews. Any further updates? Thanks

@janiceilene janiceilene removed the stale There is no recent activity on this issue or pull request label Dec 1, 2020
@janiceilene
Copy link
Contributor

@shreeya-sengupta Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨

@lecoursen
Copy link
Member

Thanks so much for opening this PR! We're not currently planning to change this right now.

@lecoursen lecoursen closed this Dec 2, 2020
jnidzwetzki pushed a commit to jnidzwetzki/docs that referenced this pull request Oct 6, 2022
* Document cagg improvements

Indexes can now be created directly on caggs by using the view name.
`ORDER BY` is supported in general, not just in the ordered-set
aggregates.

* Apply suggestions from code review

Co-authored-by: Lana Brindley <[email protected]>
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 ecosystem This issue or pull request should be reviewed by the Docs Ecosystem team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants