Skip to content

Major updates for my personal use#500

Closed
mrexodia wants to merge 7 commits intojosegonzalez:masterfrom
mrexodia:updates
Closed

Major updates for my personal use#500
mrexodia wants to merge 7 commits intojosegonzalez:masterfrom
mrexodia:updates

Conversation

@mrexodia
Copy link
Copy Markdown
Contributor

My goal is to incrementally back up a few specific repos in my org, you can see my script here: https://github.com/mrexodia/x64dbg-repo-backup.

To that end I added support for the following:

This is likely not going to be in a shape where you want to merge it as-is, so feel free to cherry-pick the commits you like or use it as inspiration. I tested it locally and it gets me the data I need so I'm happy with it, thanks a lot for your project! ☺️

@josegonzalez
Copy link
Copy Markdown
Owner

I'd be willing to pull this in (or at least parts) if you separated this out into distinct features that make it easier to review.

@mrexodia
Copy link
Copy Markdown
Contributor Author

The commits are (except maybe the last one) atomic so you can cherry-pick them and get the individual fixes you want 🙂

@Iamrodos
Copy link
Copy Markdown
Contributor

The commit e03e162 that addresses #62 moving to a pre repo last updated is a good change and addresses the items raised in the issue. Gets my +1.

@josegonzalez
Copy link
Copy Markdown
Owner

josegonzalez commented Apr 27, 2026

Please separate these into separate pull requests. If you don't want to, someone else is free to do that work for you and I will review them.

@mrexodia
Copy link
Copy Markdown
Contributor Author

The problem is that all the commits are dependent on each other because of changes to the README/CHANGELOG, so splitting them is non-trivial.

Could you take a quick glance at the approach taken in 98ead29 (it introduces GraphQL). If you are not planning to merge that there is no point for me to upstream since I have to maintain a perpetual fork anyway for my own use.

@josegonzalez
Copy link
Copy Markdown
Owner

That looks fine. Only comment I would say is asking if we can split the graphql queries into a different file.

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.

Discussions not backed up Does Not Include Reviews Backuping up multiple repositories but not the whole account

3 participants