Conversation
* Simplify package version retrieval * Add test for binary file * Add debug info * Add access token * Cleanup test * Move to private suite
When the access token is missing SAML auth a null-pointer would occur.
* Upgrade to 9.x * Fix lint issues * Simplify config file * Final fixes * Add promise rule * Add `eslint-plugin-import` * Format prettier on save * Fix import order
* Fix post-install script * Add tests * Remove log output
* feat: add support for git rerere during cherrypick conflicts When git rerere is enabled and automatically resolves conflicts during cherrypick, the process would previously hang because the tool didn't recognize that conflicts were resolved. Now detects when rerere has staged resolved files and continues the backport process smoothly. - Add getStagedFiles() function to detect rerere-resolved conflicts - Enhance cherrypick() to check for staged files when conflicts occur - Add comprehensive test coverage for rerere scenarios - Maintain backward compatibility when rerere is not used * chore: improve rerere handling + add tests - improve logic with more defensive checks against git config - differentiate between rerere.enabled and rerere.autoUpdate - add comprehensive test coverage * Add test --------- Co-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>
* Add regex support to `copySourcePRLabels` * Refactor to combine `getConfiguredTargetPRLabels` and `getSourcePRLabelsToCopy` * Add `--runInBand`
* Fix postinstall integration test for asdf-managed yarn The postinstall integration test was failing with exit code 126 when yarn is managed by asdf. This occurs because the test overrides the HOME environment variable, which breaks the asdf shim's ability to locate its configuration and execute. The issue is specific to development environments using asdf to manage tool versions. In these environments, 'yarn' is typically a shell shim at ~/.asdf/shims/yarn that requires the original HOME to function. Solution: - Detect if yarn is managed by asdf using 'asdf which yarn' - Use the actual yarn binary path instead of the shim - Use 'shell: /bin/bash' to ensure proper HOME variable handling - Falls back to 'yarn' from PATH if asdf is not available This fix ensures the test works in both asdf and non-asdf environments. * fix: suppress asdf command not found errors in integration tests Refactor yarn command resolution into shared helper that uses 'asdf which yarn' to get the actual binary path instead of the shim. This suppresses the '/bin/sh: asdf: command not found' error when HOME is overridden in tests. - Extract getYarnCommand() helper to shared integration-test-helpers.ts - Use 'which asdf' + realpath to find actual asdf binary - Use 'asdf which yarn' to resolve actual yarn binary path - Apply helper to all yarn commands in both integration test files
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.