-
Hello! I'm currently working with SymbiFlow, an open-source organization on Github, and we are looking for a way to keep files consistent across repositories, similar to what your action here accomplishes. However, we use a fork and pull request workflow and do not want bots or actions having direct access to modify upstream repositories. What do you think of adding a feature that would allow a fork and pull request workflow using this action? A possible solution could be something like the following:
Checking whether the appropriate forks already exist/creating new ones could also be included, or done by another action if it would be easier. I'd be happy to contribute if this seems like a feature that could be added. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hey, thanks for taking the time to open this discussion! I myself have no need for such a feature, but I can see the value it provides. That being said, I don't want this action to become too complicated for me to maintain and for others to use, so it depends on the implementation/scope of the feature. How do you imagine the |
Beta Was this translation helpful? Give feedback.
-
🎉 This feature was added in version v1.16.0 🎉 To use the latest version, use the Action with the uses: BetaHuhn/repo-file-sync-action@v1 Or the uses: BetaHuhn/repo-file-sync-action@latest |
Beta Was this translation helpful? Give feedback.
🎉 This feature was added in version v1.16.0 🎉
To use the latest version, use the Action with the
v1
tag:Or the
latest
tag: