search

sindresorhus / atom-editorconfig

Helps developers maintain consistent coding styles between different editors
https://atom.io/packages/editorconfig
MIT License
812 stars 80 forks source link

Move to GitHub Actions #250

Closed sindresorhus closed 1 year ago

sindresorhus commented 3 years ago

Travis no longer provides free plan for OSS.

It should be based on https://github.com/chalk/chalk/blob/main/.github/workflows/main.yml, but made to work with Atom.

the-j0k3r commented 2 years ago

Plenty of examples e.g. https://github.com/bus-stop/x-terminal/tree/master/.github/workflows minimal adaptation required obviously to suit this project

Alhadis commented 1 year ago

Atom's official sunset date is on December 15th, so between then and now, there's a slim chance of porting our tests to GitHub Actions… especially since Atom's package registry is constantly unavailable due to DDoS attacks from spam-bots publishing bullshit "packages". Which, in other words, means that the test-environment can't even be setup properly (since APM needs to make requests through Atom.io's APIs).

(FWIW, I already did port the package's test-runner to GitHub Actions in Atom-CI…)

the-j0k3r commented 1 year ago

@Alhadis for reference on our https://github.com/bus-stop/x-terminal project we have no such issues publishing/pushing updates, any of our releases continue to trigger updates within atom irrespective of any failures.

The 500 errors are generic anyway, indicates some server side something only and shouldn't affect any publishing.