Update GitHub action dependencies and add Dependabot scanning

[dougwaldron]

Some GitHub actions need to be updated:

• Code scanning: deprecation of CodeQL Action v2 - The GitHub Blog
• GitHub Actions: Transitioning from Node 16 to Node 20 - The GitHub Blog

This PR also enables Dependabot version updates for GitHub actions so future PRs will be automatically created:

• Keeping your actions up to date with Dependabot - GitHub Docs

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[tom-karasch]

Doug, my main branch is what was done before Phase-II. Should I merge this into main, and Publish to Prod and UAT (until we go to UAT with Phase-II) ?? I was thinking to put it in my Dev Branch, but, now that I think about it, it probably should go in Main, then it will be included when I merge my Phase-II changes into Main. (Sorry, just thinking out loud. LOL)

[dougwaldron]

I changed the base branch to Dev. These changes will have no effect on what is published to the web server; they only affect the GitHub actions, which should be running on PRs, etc., so this should go wherever you're doing your work, i.e., Dev. If you still make updates to main, you could merge into main also, but I'd say that's overkill, since the deprecations don't take effect until December.

BTW, on the repo settings tab, you can change the default branch to Dev, so all PRs will use that as the base branch.

[tom-karasch]

I changed the base branch to Dev. These changes will have no effect on what is published to the web server; they only affect the GitHub actions, which should be running on PRs, etc., so this should go wherever you're doing your work, i.e., Dev. If you still make updates to main, you could merge into main also, but I'd say that's overkill, since the deprecations don't take effect until December.

Thanks for the clarification. I am at a good point at the moment to merge it.

BTW, on the repo settings tab, you can change the default branch to Dev, so all PRs will use that as the base branch.
AH, thanks for that! That is a huge help! I did not see that!

[tom-karasch]

BTW, on the repo settings tab, you can change the default branch to Dev, so all PRs will use that as the base branch.

Doug, I only see this in my account settings. I do not see settings tab for only this repo. Am I lacking rights to see it? I have searched all over the repo.