Step 2 not updating README to Step 3

[rluna319]

Hello,

I am having an issue where upon completing the instructions in the README for Step 2 of the Release-based workflow tutorial, the README does not update and move to Step 3.

I didn't spot this discussion board link till after I had posted an issue on the official relelase-based-workflow repo. I tagged the issue as a bug and I put the details there.

[jmbvstepback]

Hi, the same here. Non updating to Step 3 and completely blocked in the progress on the associated course :-( . Any help is welcome....

[jmbvstepback]

Update: In my case, updating the case was enough to pass from Step2 to Step3. Check the name of the function is agree in case with:

function calculateNumbers

[sinsukehlab]

Your issue is on the "Code with Copilot" course. It's different from the issue that the original post discusses.

[sinsukehlab]

According to the network graph, it seems that you didn't create your new branches from the main branch.
The Step 2 workflow ran on the release-v1.0 branch and skipped the update job because the Step was not 2 but 0 on the release-v1.0 branch.

[sinsukehlab]

I haven't instructed the author of this question to merge to the main branch. According to the Step 2 markdown, one should create a new branch off of the main branch, edit base.css, and open and merge a PR with release-v1.0 as the base and the new branch as the compare.

[zzzbra]

I don't think that's accurate:

Open a pull request with release-v1.0 as the base branch, and your new branch as the compare branch.

What then gets merged to in the subsequent commands is the release branch. If there's no update to main, the workflow won't trigger, unless I am mistaken.

[sinsukehlab]

You made the same mistake as the questioner. You should have created your new branch from the main branch, not from the release-v1.0 branch.
The workflow on the release-v1.0 branch will be triggered. Actually, you have also triggered the workflow. The step won't be updated unless the step on the release-v1.0 branch is 2 after merging.

[zzzbra]

The assumption that the original change be checked out off of main is not implied anywhere, and is pretty odd. If one has a release branch they are prepping, and knows a change is meant for it, they are not likely to check out off of the divergent main branch. Either explicitly state this assumption in the instructions, or fix the logic of the workflow updates to match the more real world workflow, or folks are liable to continue adding to this thread.

[sinsukehlab]

The assumption is explicitly stated in the instructions.

⌨️ Activity: Update base.css

1. Create a new branch off of the main branch and change the body CSS declaration in base.css to match what is below. This will set the page background to black.

body {
    background-color: black;
}

1. Open a pull request with release-v1.0 as the base branch, and your new branch as the compare branch.
2. Fill in the pull request template to describe your changes.
3. Click Create pull request.

[cechrisha]

I had a problem where I wasn't able to go to step 3 > 4.

I could not figure it out. Ended up deleting the entire repository and redoing all the steps exactly the same.

It ended up working the second time around.

IDK if this will help you but maybe give that a try?

[rluna319]

That might have worked too if I followed the instructions properly in the new repo. I wanted to learn a bit more by troubleshooting the issue without deleting and forking the repo again.

I solved the issue thanks to @sinsukehlab. You can view the process in the answer thread. But thank you for your contribution to my issue!

[cechrisha]

Glad you were able to figure it out!!

[HakaCode]

Hello, I would like some help if possible...
I have an error when automatically updating the readme, after Step 7: Create release v1.0.1

[sinsukehlab]

I can't find any mistakes in your repo. Try triggering the Step 7 workflow manually (workflow_dispatch).