Error in developer workflow after adding doxygen build

[AlysonStahl-NOAA]

After merging #187, I'm getting the following error with the developer workflow:

Run actions/deploy-pages@v1
Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
at Function. (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/oidc-utils.js:71:1)
at Generator.next ()
at /home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/oidc-utils.js:8:1
at new Promise ()
at webpack_modules.8041.__awaiter (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/oidc-utils.js:4:1)
at Function.getIDToken (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/oidc-utils.js:57:1)
at Object. (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/core.js:315:1)
at Generator.next ()
at /home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/@actions/core/lib/core.js:27:1
at new Promise ()
Error: Ensure GITHUB_TOKEN has permission "id-token: write".

[AlysonStahl-NOAA]

@edwardhartnett It looks like Wesley's PR is passing checks and it's up to date. Is it just failing for me because I'm working on my own fork?

[edwardhartnett]

Maybe. I need to work on that some more tomorrow. YOu can just comment out the part of the developer.yml workflow that is causing trouble in your branch, and proceed with your work while I figure it out... Ed

…

On Wed, Jul 17, 2024 at 1:02 PM AlysonStahl-NOAA ***@***.***> wrote: @edwardhartnett <https://github.com/edwardhartnett> It looks like Wesley's PR is passing checks and it's up to date. Is it just failing for me because I'm working on my own fork? — Reply to this email directly, view it on GitHub <#191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJIOMMBQSJHFIMXEDOL6CFDZM25QFAVCNFSM6AAAAABLBFZ7GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZUGAZTMOJSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Edward Hartnett CIRES/NOAA EMC

[edwardhartnett]

OK, the problem was that I was running the documentation update in the developer workflow, which runs for PRs and pushes.

We don't want the documentation updated for PRs, just pushes. That is happening now. I am still experimenting with it, but I think this issue is resolved.