ci: update cf pages user agent name

[mujahidkay]

Description

When working on sites deployed via CF Pages, devs have been having issues trying to debug build failures. We have a custom action that fetches build logs from CF and displays them in a github workflow by posting a comment with an easy to access logs link.

The root cause was a change in user agent name (presumably from CF's side). Have verified this is a user agent mismatch by forking this repo to my personal account, and adding relevant debug info. [github triggers issue_comment triggered workflows from the default branch hence the workaround for debugging]

Can verify name mismatch here

Debugging information:
Is Pull Request: true
Comment Author: cloudflare-workers-and-pages[bot]
Condition Met: false

[cloudflare-workers-and-pages]

Deploying documentation with    Cloudflare Pages

Latest commit:	654b102
Status:	✅  Deploy successful!
Preview URL:	https://a1d07e92.documentation-7tp.pages.dev
Branch Preview URL:	https://logs-fetcher-debug.documentation-7tp.pages.dev

View logs

[toliaqat]

Changes in cf-logs-fetcher.yml only get triggered after it has been merged because it is triggered on the comment of the PR and not the original PR itself.

[mujahidkay]

Changes in cf-logs-fetcher.yml only get triggered after it has been merged because it is triggered on the comment of the PR and not the original PR itself.

yep, i'm aware. issue_comment based triggers use the workflow from default branch.

I created a fork of this repo that I will set up using a personal CF account and debug that way by pushing directly to master/main.

[Muneeb147]

Change looks good as per the verification you did.
But I'm curious if we can have any CF thread where they changed their botname. Did we find something online or may be in their release notes/log?

[mujahidkay]

Change looks good as per the verification you did. But I'm curious if we can have any CF thread where they changed their botname. Did we find something online or may be in their release notes/log?

None that I could find. This is the only relevant changelog (remotely) that is relevant. I would assume it made changes to the overarching, unified GitHub app as well.