We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I think I misinterpret the meaning of owner.
owner
I am trying to sync not just from upstream -> fork but between fork-A and fork-B in different orgs.
Syncing kaovilai/velero
main
vmware-tanzu/velero:main
release-1.9
vmware-tanzu/velero:release-1.9
oadp-1.0
openshift/velero:oadp-1.0
See my workflow
Is this possible with this action?
The text was updated successfully, but these errors were encountered:
Made a feature request in octokit/rest.js#222 as it's not obvious to me if it's implementable right now through that library.
Sorry, something went wrong.
Resolved. See my changes here. master...b89779a#diff-7934bf411fea192ad8cd69e0a12911648a2842cb0f2409a8fb67b41b7069d757R68
I will leave this open just in case you want to incorporate this.
There is a way to implement this without breaking existing syntax while enabling more flexibility.
No branches or pull requests
I think I misinterpret the meaning of
owner
.I am trying to sync not just from upstream -> fork
but between fork-A and fork-B in different orgs.
Syncing kaovilai/velero
main
withvmware-tanzu/velero:main
release-1.9
withvmware-tanzu/velero:release-1.9
oadp-1.0
withopenshift/velero:oadp-1.0
See my workflow
Is this possible with this action?
The text was updated successfully, but these errors were encountered: