A glitchy but lovable microblogging server
Go to file
Claire 155424e52f [Glitch] Run eslint --fix
I don't like it changing files this way, but it's basically what
c49213f0ea and a few others did.
2023-02-03 20:52:07 +01:00
.circleci
.devcontainer
.github Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
app [Glitch] Run eslint --fix 2023-02-03 20:52:07 +01:00
bin
chart
config Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
db Merge branch 'main' into glitch-soc/merge-upstream 2023-01-18 17:38:11 +01:00
dist
lib Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
log Initial commit 2016-02-20 22:53:20 +01:00
public
spec Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
streaming
vendor
.browserslistrc
.buildpacks
.codeclimate.yml
.deepsource.toml
.dockerignore
.editorconfig
.env.production.sample
.env.test
.env.vagrant
.eslintignore
.eslintrc.js Enable ESLint jsx-a11y/recommended ruleset (#23309) 2023-01-30 14:18:12 +09:00
.foreman
.gitattributes
.gitignore
.gitmodules
.haml-lint.yml
.nanoignore
.nvmrc
.prettierignore
.prettierrc.js
.profile
.rspec
.rubocop.yml
.ruby-gemset
.ruby-version
.slugignore
.yarnclean
app.json
Aptfile
AUTHORS.md
babel.config.js
Capfile
CHANGELOG.md Bump version to 4.1.0rc3 (#23384) 2023-02-03 16:39:38 +01:00
CODE_OF_CONDUCT.md
config.ru
CONTRIBUTING.md
crowdin-glitch.yml
crowdin.yml
docker-compose.yml
Dockerfile
FEDERATION.md
Gemfile Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
Gemfile.lock Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
ide-helper.js
jest.config.js
jsconfig.json
LICENSE
package.json Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00
postcss.config.js
priv-config
Procfile
Procfile.dev
Rakefile
README.md
scalingo.json
SECURITY.md
stylelint.config.js
Vagrantfile
yarn.lock Merge branch 'main' into glitch-soc/merge-upstream 2023-02-03 19:23:27 +01:00

Mastodon Glitch Edition

Now with automated deploys!

Build Status Code Climate

So here's the deal: we all work on this code, and anyone who uses that does so absolutely at their own risk. can you dig it?