Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite Curator #239

Merged
merged 18 commits into from Jun 3, 2019
Merged

Rewrite Curator #239

merged 18 commits into from Jun 3, 2019

Conversation

f-f
Copy link
Member

@f-f f-f commented Jun 2, 2019

As Spago's CI infrastructure expands to automate more and more so we have to do less by hand, the existing approach with a bunch of bash scripts wasn't really scaling, so I ported the whole thing to a self-contained Haskell binary.

This is run on some machine I have, but the only requirements for anyone to run it are:

  • a GitHub token
  • having an ssh key authenticated to spacchetti/spago, spacchetti/package-sets-metadata, and purescript/package-sets. This is because we push branches there, but the program can be easily changed so that the branches are pushed elsewhere if needed

Things that Curator now does:

  • update the package-sets version here in spago
  • keep the package index up to date in package-sets-metadata
  • open PRs to package-sets for new versions of its packages (this is the only actually new thing)

@f-f f-f merged commit 2b1c833 into master Jun 3, 2019
@f-f f-f deleted the rewrite-curator branch June 3, 2019 18:49
elliotdavies pushed a commit to elliotdavies/spago that referenced this pull request Jul 1, 2019
As Spago's CI infrastructure expands to automate more and more so we have 
to do less by hand, the existing approach with a bunch of bash scripts wasn't
really scaling, so I ported the whole thing to a self-contained Haskell binary.

This is run on some machine I have, but the only requirements for anyone to 
run it are:
* a GitHub token
* having an ssh key authenticated to `spacchetti/spago`, 
  `spacchetti/package-sets-metadata`, and `purescript/package-sets`. 
  This is because we push branches there, but the program can be easily 
  changed so that the branches are pushed elsewhere if needed

Things that Curator now does:
* update the package-sets version here in spago
* keep the package index up to date in `package-sets-metadata`
* open PRs to package-sets for new versions of its packages 
  (this is the only actually new thing)
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.

None yet

1 participant