You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 20, 2022. It is now read-only.
Motivation: For Cawemo we currently manage our tasks and open problems via Github Issues and Milestones and it would be great to backup them alongside our code, maybe even more important than the code since nearly every developer has a local checkout of the code. (We don't use Github's Pull Requests for now.)
I care about both, open and closed issues (for different reasons) and their metadata like labels, assignees, milestones and comments. Some of our issues have attachments/embedded pictures (e.g. https://github.com/camunda/cawemo/issues/1123), they are not critical but would be a nice addon.
Persistence: Since this about backups only, in contrast to git repositories the restore of issues is way harder and does not need to be solved now. Facing that, some kind of barely human readable format (YAML > JSON) would be nice, having each issue in a separate file and the whole bunch then compressed afterwards and stored alongside in the S3 bucket. We have around 200 open and 1000 closed issues now. I have no preference for the directory structure, for file browsing experience it maybe should not be all in one directory.
Motivation: For Cawemo we currently manage our tasks and open problems via Github Issues and Milestones and it would be great to backup them alongside our code, maybe even more important than the code since nearly every developer has a local checkout of the code. (We don't use Github's Pull Requests for now.)
I care about both, open and closed issues (for different reasons) and their metadata like labels, assignees, milestones and comments. Some of our issues have attachments/embedded pictures (e.g. https://github.com/camunda/cawemo/issues/1123), they are not critical but would be a nice addon.
Persistence: Since this about backups only, in contrast to git repositories the restore of issues is way harder and does not need to be solved now. Facing that, some kind of barely human readable format (YAML > JSON) would be nice, having each issue in a separate file and the whole bunch then compressed afterwards and stored alongside in the S3 bucket. We have around 200 open and 1000 closed issues now. I have no preference for the directory structure, for file browsing experience it maybe should not be all in one directory.