Skip to content

Document how the update automation works #47

@fwilhe

Description

@fwilhe

Because it came up in a conversation

We have to manually create a comment to map the ci workflow run to the pr we create as part of the automation as we do it here. This is due to the fact that github on purpose does not trigger workflow runs for prs that are created in the automation as documented here.

The sad thing is that this does not give us this nice integration of ci results in the pr, as you can see in this manually created pr

Screenshot 2024-11-29 at 10 51 11

It rather looks like this (0 checks, which is not true, but the mapping is missing):

Screenshot 2024-11-29 at 10 51 51

As a workaround I've made it so we at least comment the workflow run in the pr. This seems to work reliably from what I can tell so far. It's not perfect but it's the best thing I could come up with so far.

Screenshot 2024-11-29 at 10 52 29

Leaving this issue open as documentation, and maybe as a reminder to look for a better solution in the future.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions