😕

Open
#135 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
elixir, git, github
Domain
devops, documentation, tooling

Research direction

The issue names no files, tests, or entry points. Start by reviewing the repository and the linked security report, then clarify the scope for backing up repository code, issues, and pull requests and for scheduling a Git hook. Done would require the listed backup, hook, and documentation goals to be specified and completed.

Written by the indexing model from the issue text.

Description

help wanted priority-2

https://www.zdnet.com/article/a-hacker-is-wiping-git-repositories-and-asking-for-a-ransom
image

Todo

  • Revive this project
  • Backup all our repos
    • code
    • issues
  • schedule a Git Hook that performs the backup on each commit or issue/PR update
  • document it so others can use it
Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.