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
We've added this workflow to our repo but it seems it didn't do much
https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/1342/checks?check_run_id=1708125282#step:2:1
Run tibdex/backport@v1 with: github_token: *** title_template: [Backport {{base}}] {{originalTitle}}
config:
name: Backport on: pull_request: types: - closed - labeled jobs: backport: runs-on: ubuntu-20.04 name: Backport steps: - name: Backport uses: tibdex/backport@v1 with: github_token: ${{ secrets.BACKPORT_BOT_TOKEN }}
No logs were printed to trace back where the problem's coming from.
The text was updated successfully, but these errors were encountered:
Doesn't matter, it backported it on merge 🤦🏻
Sorry, something went wrong.
No branches or pull requests
We've added this workflow to our repo but it seems it didn't do much
https://github.com/SumoLogic/sumologic-kubernetes-collection/pull/1342/checks?check_run_id=1708125282#step:2:1
config:
No logs were printed to trace back where the problem's coming from.
The text was updated successfully, but these errors were encountered: