Skip to content

feat: Automate using GitHub Actions #15

@radiantly

Description

@radiantly

From what I understand, to update the repo, we still require to periodically run harwest codeforces or harwest atcoder. Instead, we could also offer the option of automatically setting up a GitHub Action that runs harwest and updates the repo daily. (using the cron directive in the .yml file)

A few ideas I have in mind:

  • During initialization, we detect if the repository url is a GitHub repo. If yes, we prompt whether they are okay with automatic updates by a GitHub Action.
  • If yes, we also add a .github/workflows/harwest.yml to the initial repo.
  • Currently, the configuration data is stored in lib/resources. This will have to be changed to the repo itself (maybe a .config folder).
  • If the user runs harwest codeforces or the like locally, we will pull first to receive the latest updated repo.

P.S. Great work with the project - really slick!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions