Publish with incremental-release [skip ci][skip version] (#31)

Hi 👋 , I'm from team Gaudi. This PR is to fix an issue we identified with incremental-release where changes on maintenance branches (e.g. hotfixes on release/2022.9.x) are being published as "latest" and being used by the current BSI, instead of it using only the main branch.

This change moves publishing into incremental-release, which will tag maintenance branch releases appropriately so that they're not treated as latest. We recently made similar changes with match-lms-release, e.g. here: https://github.com/Brightspace/consistent-evaluation/pull/1084

Note that we will also need to make these changes on any active maintenance branches, so that they use the proper pipeline.

If this repo supports squash merging, then this PR won't trigger a release - I will include [skip ci][skip version] in the merge commit.

Required action from your team 👀

Please let me know if there are any maintenance branches on this repo that may receive hotfixes in the future, so that we can also backport these changes there. This includes any maintenance branch that may be made in the future for 20.22.10.

Thanks!

More info

Rally: https://rally1.rallydev.com/#/?detail=/userstory/646357845471&fdp=true

Yep, that's right. It's easy to spot because the previous release action defined the env var NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} when running npm publish.

Hi 👋 , I'm from team Gaudi. This PR is to fix an issue we identified with incremental-release where changes on maintenance branches (e.g. hotfixes on release/2022.9.x) are being published as "latest" and being used by the current BSI, instead of it using only the main branch.

This change moves publishing into incremental-release, which will tag maintenance branch releases appropriately so that they're not treated as latest. We recently made similar changes with match-lms-release, e.g. here: https://github.com/Brightspace/consistent-evaluation/pull/1084

Note that we will also need to make these changes on any active maintenance branches, so that they use the proper pipeline.

If this repo supports squash merging, then this PR won't trigger a release - I will include [skip ci][skip version] in the merge commit.

Required action from your team 👀

Please let me know if there are any maintenance branches on this repo that may receive hotfixes in the future, so that we can also backport these changes there. This includes any maintenance branch that may be made in the future for 20.22.10.

Thanks!

More info

Rally: https://rally1.rallydev.com/#/?detail=/userstory/646357845471&fdp=true

Just chiming in - the demo works fine (though a bit slow, and definitely running hot) on my Macbook Pro 2019. The engine is very cool, keep up the awesome work! 👍

hoping to find a way to make the dropdown disappear

😭 Oh no! It's been such a hassle not having it!

But I suppose on a user end, it would be possible to remove with a script / browser extension - find the element by CSS query and set its display to none. Seems super unlikely that there would be any GitHub-side setting to hide it though.

Publish with incremental-release [skip ci][skip version] (#190)

Hi 👋 , I'm from team Gaudi. This PR is to fix an issue we identified with incremental-release where changes on maintenance branches (e.g. hotfixes on release/2022.9.x) are being published as "latest" and being used by the current BSI, instead of it using only the main branch.

This change moves publishing into incremental-release, which will tag maintenance branch releases appropriately so that they're not treated as latest. We recently made similar changes with match-lms-release, e.g. here: https://github.com/Brightspace/consistent-evaluation/pull/1084

Note that we will also need to make these changes on any active maintenance branches, so that they use the proper pipeline.

If this repo supports squash merging, then this PR won't trigger a release - I will include [skip ci][skip version] in the merge commit.

Required action

Please let me know if there are any maintenance branches on this repo that may receive hotfixes in the future, so that we can also backport these changes there. This includes any maintenance branch that may be made in the future for 20.22.10.

Thanks!

More info

Rally: https://rally1.rallydev.com/#/?detail=/userstory/646357845471&fdp=true

Hi 👋 , I'm from team Gaudi. This PR is to fix an issue we identified with incremental-release where changes on maintenance branches (e.g. hotfixes on release/2022.9.x) are being published as "latest" and being used by the current BSI, instead of it using only the main branch.

This change moves publishing into incremental-release, which will tag maintenance branch releases appropriately so that they're not treated as latest. We recently made similar changes with match-lms-release, e.g. here: https://github.com/Brightspace/consistent-evaluation/pull/1084

Note that we will also need to make these changes on any active maintenance branches, so that they use the proper pipeline.

If this repo supports squash merging, then this PR won't trigger a release - I will include [skip ci][skip version] in the merge commit.

Required action

Please let me know if there are any maintenance branches on this repo that may receive hotfixes in the future, so that we can also backport these changes there. This includes any maintenance branch that may be made in the future for 20.22.10.

Thanks!

More info

Rally: https://rally1.rallydev.com/#/?detail=/userstory/646357845471&fdp=true

Not sure if this was announced anywhere, but it looks like the email dropdown is back for squash merges, on both personal and org repos! 🎉 Thanks to whoever was involved in restoring that behaviour!

Just a bit of house-keeping on this document:

• fixed typo in persist-credentials
• fixed indenting inside the numbered list
• added match-lms-release to the list of relevant workflows

fix: Typo, indenting, and list of workflows (#92)

• fix: Typo, indenting, and list of workflows

• Update docs/branch-protection.md

Co-authored-by: Stacey Van Herk 13419300+svanherk@users.noreply.github.com

Co-authored-by: Stacey Van Herk 13419300+svanherk@users.noreply.github.com

Update docs/branch-protection.md

Co-authored-by: Stacey Van Herk 13419300+svanherk@users.noreply.github.com

Just a bit of house-keeping on this document:

• fixed typo in persist-credentials
• fixed indenting inside the numbered list
• added match-lms-release to the list of relevant workflows

Add readme