Skip to content

Better control the scope of the "Run sipify" action #62313

Description

@DelazJ

What is the bug or the crash?

Today, from GitHub interface, I synced my master branch with the upstream one. Probably just after e186ae6.
It resulted in my branch

Image

Image

While from upstream branch the history is

Image

Looks like my branch ran locally the sipify action, diverging then from the upstream master.

I don't know if we should limit the action scope to the qgis/QGIS repo or only run it in particular contexts (PR?) or disable it on my side, so I'm opening this issue report, so that most qualified people fix it/advise appropriately.

Steps to reproduce the issue

See above

Versions

https://github.com/qgis/QGIS/

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugEither a bug report, or a bug fix. Let's hope for the latter!CI/GitHub-Actionsissues related to GitHub Actions

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions