Replies: 2 comments
|
You could create a postprocessing script that fetches the committed file contents (via the GitHub API) and compares it to the new file contents. The filename is passed as the first argument ( Alternatively, you could also create another step in your workflow that looks at the last commit's diff and works from there. |
0 replies
|
This is something I'm interested in to. I was thinking about doing it via the git diff, but all I need is to seed the changes into a in-memory db |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What's the best approach to diff data between 2 versions? I'd like to build workflows that compares data across versions and take some action.
All reactions