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

Revert to 0 and update YAML files #10

Merged
merged 22 commits into from
Aug 25, 2022
Merged

Revert to 0 and update YAML files #10

merged 22 commits into from
Aug 25, 2022

Conversation

sinsukehlab
Copy link
Contributor

@sinsukehlab sinsukehlab commented Aug 4, 2022

  • Revert some commits by @github-actions to reset STEP to 0
  • (Update update-step.sh to enable it to close Step 0 in README.md)
  • Fix the conditional expressions in the YAML files
  • Edit the YAML files so that they could use skills/action-update-step@v1 to update steps
  • Fix the YAML files so that the workflows could function without any error or skip
  • Change the style of conditional expressions in the YAML files
  • Clearly indicate the wait in README.md
  • Enable echoing workflow commands

Why:

The latest commits by @github-actions have updated STEP, README.md, and _sidebar.md.
STEP should be set to 0 when generated, and then be updated to 1 by @github-actions closing Step 0 in README.md.
Also, a check in Step 3 is skipped even if the learner follows the instructions.

What's being changed:

  • I reverted recent commits by @github-actions to reset STEP to 0.
  • I then updated update-step.sh to enable it to close Step 0 in README.md. (now deprecated)
  • I fixed the conditional expressions in the YAML files.
  • I edited the YAML files so that they could use skills/action-update-step@v1 to update steps.
  • I fixed the YAML files so that the workflows could function without any error or skip.
  • 3-fix-broken-sidebar.yml is now triggered by pull_request and checks if github.event.pull_request.body contains 'Closes'.
  • I changed the style of conditional expressions in the YAML files.
  • I clearly indicated the wait in README.md.
  • I enabled echoing workflow commands.

Check off the following:

  • For workflow changes, I have verified the Actions workflows function as expected.
  • For content changes, I have reviewed the style guide.

This was referenced Aug 6, 2022
Make actions run unless the repository is template
@sinsukehlab
Copy link
Contributor Author

I have fixed workflows lest Actions should run in this repository.

@sinsukehlab sinsukehlab mentioned this pull request Aug 6, 2022
2 tasks
A minor change in 0-start.yml corresponds to an update on update-step.sh
@sinsukehlab
Copy link
Contributor Author

sinsukehlab commented Aug 12, 2022

Somewhat duplicate of #13
However, Step 3 is still open in README.md.
YAML files still contain syntax errors.

@sinsukehlab
Copy link
Contributor Author

sinsukehlab commented Aug 12, 2022

Hmm.... 🤔
I am really unhappy about #13 because it is not a real solution to the problem. 😞
I doubt that they have verified the Actions workflows function as expected.
I reopen this PR now. 👐

@sinsukehlab sinsukehlab reopened this Aug 12, 2022
@sinsukehlab
Copy link
Contributor Author

I have made a commit to make workflows use skills/action-update-step@v1 to update steps.
I have checked if the Action workflows function, and have found an error.
I will fix this error.

@sinsukehlab
Copy link
Contributor Author

I will change the trigger for 3-fix-broken-sidebar.yml.
on: issue_comment

@sinsukehlab
Copy link
Contributor Author

I will also fix YAML style.
Cf. #14

@sinsukehlab
Copy link
Contributor Author

Some checks such as "Check if commented issue is closed and marked as duplicate" in Step 1 are now just skipped if the conditions are not met.
I will leave them behind for now.
What do you think?

Now the trigger is on issue_comment

Also fix YAML style for multi-line conditinal expressions (skills#14)

Fix some 'TBD' comments
@sinsukehlab
Copy link
Contributor Author

Multi-line conditional expressions did not work well.
I will use single-line ones.

Cf. skills#14

Also change the trigger for 3-fix-broken-sidebar.yml
@sinsukehlab
Copy link
Contributor Author

sinsukehlab commented Aug 23, 2022

I have finally fixed this course! 🎉
I have generated a repository and verified the Actions workflows function as expected, i.e. without any skips if the learner follows the instructions.

@sinsukehlab
Copy link
Contributor Author

sinsukehlab commented Aug 25, 2022

@heiskr @a-a-ron Hello. I strongly propose to merge this PR so that it can improve your great course. I reverted some commits by @github-actions and then updated GitHub Actions workflows. Now the workflows function as expected completely.

Why:

The latest commits by @github-actions have updated STEP, README.md, and _sidebar.md.
STEP should be set to 0 when generated, and then be updated to 1 by @github-actions closing Step 0 in README.md.
Also, a check in Step 3 is skipped even if the learner follows the instructions.

What's being changed:

  • I reverted recent commits by @github-actions to reset STEP to 0.
  • I then updated update-step.sh to enable it to close Step 0 in README.md. (now deprecated)
  • I fixed the conditional expressions in the YAML files.
  • I edited the YAML files so that they could use skills/action-update-step@v1 to update steps.
  • I fixed the YAML files so that the workflows could function without any error or skip.
  • 3-fix-broken-sidebar.yml is now triggered by pull_request and checks if github.event.pull_request.body contains 'Closes'.
  • I changed the style of conditional expressions in the YAML files.
  • I clearly indicated the wait in README.md.
  • I enabled echoing workflow commands.

Check off the following:

  • For workflow changes, I have verified the Actions workflows function as expected.
  • For content changes, I have reviewed the style guide.

@sinsukehlab sinsukehlab changed the title Revert to 0 and update update-step.sh Revert to 0 and update YAML files Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants