Skip to content

fix: pass changed README files to create-pull-request one per line - #36

Merged
goruha merged 1 commit into
mainfrom
fix/add-paths-newline
Nov 12, 2026
Merged

goruha merged 1 commit into
mainfrom
fix/add-paths-newline

Conversation

@osterman

Copy link
Copy Markdown
Contributor

what

  • Add a files output to the readme step: the changed files, one per line.
  • Use it for add-paths in the Create Pull Request step.
  • file and the readme_file output do not change. They stay space-separated, because git-auto-commit file_pattern (commit_method: commit) needs that.

why

references

  • Repos pin @v3. After merge, move the v3 tag to the new release so all repos get the fix.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JW9Go7ujHrXLWGtnmbgynt

add-paths splits on newlines or commas. The readme step returned a
space-separated list, so when more than one file changed, git add got
"README.md src/README.md" as one path and the job failed.
@mergify

mergify Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

These changes were released in v3.2.0.

@goruha
goruha merged commit 083b453 into main Nov 12, 2026
9 checks passed
@goruha
goruha deleted the fix/add-paths-newline branch November 12, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants