Edits to new instructions

[SirSpidey]

Description

Updates to the updating instructions. Check that these make sense. Merges into refactor branch.

Release required?

• [ ] No release
• [ ] Patch release (x.x.X)
• [ ] Minor release (x.X.x)
• [ ] Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• [ ] If relevant, a test for the change is included or updated with this PR.
• [ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[SirSpidey]

@Aashiq-J a couple of comments or questions

• "...Workspace ID for the project towards the right-hand side of the screen."

  • I didn't see any workspace IDs there. Did you mean on the Manage page, under ID?

    

• I got rid of the docs link about the API keys because I didn't think it applied. You're not "CRUD-ing" the key here. Let me know if you were trying to provide some other information.

[Aashiq-J]

@SirSpidey , You missed these steps:

[SirSpidey]

@Aashiq-J @ocofaigh Pushed up some changes based on your review.

Question Are the 3.x.x and 4.xx labels meant to indicate any version (as in v3.0.0 and later) or are they placeholders for specific versions that we will change?

If they mean update v3 to v4, let's remove the .x.x and use version 3 and 4. The script can stay as it is as far as i'm concerned.

---

[ocofaigh]

@SirSpidey it means update v3 to v4, so agree lets remove the .x.x