about summary refs log tree commit diff
path: root/.github
AgeCommit message (Collapse)Author
2022-03-15Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `README.md`: Upstream changed their README, we have a completely different one. Kept our README.
2022-03-15Replace metadata-action type to match (#17802)Yamagishi Kazutoshi
2022-03-15Remove references to discourse.joinmastodon.org (#17797)Eugen Rochko
Remove broken CODEOWNERS file Add sponsor.joinmastodon.org to FUNDING.yml
2022-02-23Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `.github/workflows/build-image.yml`: Upstream changed the workflow a bit. Conflict comes from us pushing to ghcr while upstream pushes to dockerhub. Ported the upstream changes while still pushing to ghcr.
2022-02-23Skip Docker Hub login for pull requests (#17625)Yamagishi Kazutoshi
* Skip Docker Hub login for pull requests * Add support pr tag
2022-02-17Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `db/schema.rb`: Conflict due to glitch-soc adding the `content_type` column on status edits and thus having a different schema version number. Solved by taking upstream's schema version number, as it is higher than glitch-soc's.
2022-02-14Remove protobuf dependencies (#17539)Yamagishi Kazutoshi
2022-02-06Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `CHANGELOG.md`: Upstream added newlines. Conflicts are because the CHANGELOG was independently merged from 3.4.6 on last security update. Took upstream's version. - `app/helpers/context_helper.rb`: Conflicts because of extra vocabulary in glitch-soc. The conflicts were actually handled in last security merge. Kept our version.
2022-02-05Update build-image.yml (#17454)potpro
2021-12-18Revert "Change workflow to push to Docker Hub (#16980)"Claire
This reverts commit 4b616c4f0a2158883034cd756391bd70265b787d.
2021-11-25Merge branch 'main' into glitch-soc/merge-upstreamClaire
2021-11-24Better ordering for bug report issue template (#17019)trwnh
Logically, it makes more sense to provide the steps leading up to the bug before asking what the bug is. This change moves "steps to reproduce" above "expected behavior" and "actual behavior" to enforce the above progression and logical flow.
2021-11-19Merge branch 'main' into glitch-soc/merge-upstreamClaire
2021-11-18Ruby 3.0.2 Upgrade (#16982)Shlee
* Update .ruby-version * Update Gemfile * Update Gemfile.lock * Update Dockerfile * Update check-i18n.yml * Update config.yml * Update config.yml
2021-11-16Add manual GitHub Actions runs (#17000)Eugen Rochko
2021-11-14Change workflow to push to Docker Hub (#16980)Eugen Rochko
2021-11-13Merge branch 'main' into glitch-soc/merge-upstreamClaire
2021-11-12Build container image by GitHub Actions (#16973)Yusuke Nakamura
* Build container image by GitHub Actions * Trigger docker build only pushed to main branch * Tweak tagging imgae - "edge" is the main branch - "latest" is the tagged latest release
2021-07-13Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `CONTRIBUTING.md`: Upstream file has changed and we're quoting it. Ported the changes. - `README.md`: Upstream file has changed but we have a completely different one. Kept our version. - `lib/mastodon/version.rb`: Upstream has changed from `tootsuite/mastodon` to `mastodon/mastodon`, but we're still `glitch-soc/mastodon`. Kept our version. - `spec/presenters/instance_presenter_spec.rb`: Upstream has changed from `tootsuite/mastodon` to `mastodon/mastodon`, but we're still `glitch-soc/mastodon`. Kept our version.
2021-07-13Change references to tootsuite/mastodon to mastodon/mastodon (#16491)Claire
* Change references to tootsuite/mastodon to mastodon/mastodon * Remove obsolete test fixture * Replace occurrences of tootsuite/mastodon with mastodon/mastodon in CHANGELOG And a few other places
2021-06-30Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `.github/ISSUE_TEMPLATE/bug_report.md`: Removed upstream, while we had a checkbox telling people to check if the issue was present upstream. Removed the file as well.
2021-06-25Replace to issue form (#16429)Yamagishi Kazutoshi
2021-06-03Merge branch 'main' into glitch-soc/merge-upstreamClaire
2021-06-01Fix spelling error in i18n workflow (#16326)koyu
2021-05-27Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `README.md`: Upstream's README got updated, but we have a completely different one. Kept ours.
2021-05-22Add Actions for check i18n (#16285)Yamagishi Kazutoshi
2020-11-20Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - `.github/ISSUE_TEMPLATE/bug_report.md`: Upstream added the `bug` label to bug reports. Did the same. - `app/services/fan_out_on_write_service.rb`: Upstream put DMs back into timelines, glitch-soc was already doing it. Ignored upstream changes.
2020-11-14Apply label automatically when issue creation from template (#15154)Yamagishi Kazutoshi
2020-10-06Exclude dependency updates other than direct dependencies (#14944)Yamagishi Kazutoshi
2020-06-30Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - `.env.production.sample`: Upstream deleted it, I decided to keep it. - `package.json`: Upstream updated a dependency textually too close to wavesurfer.js which has been deleted from upstream but is kept in glitch-soc for now.
2020-06-29Add GitHub SponsorsEugen Rochko
2020-06-09Disable dependabotThibaut Girka
2020-06-09Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - `app/controllers/activitypub/collections_controller.rb`: Conflict due to glitch-soc having to take care of local-only pinned toots in that controller. Took upstream's changes and restored the local-only special handling. - `app/controllers/auth/sessions_controller.rb`: Minor conflicts due to the theming system, applied upstream changes, adapted the following two files for glitch-soc's theming system: - `app/controllers/concerns/sign_in_token_authentication_concern.rb` - `app/controllers/concerns/two_factor_authentication_concern.rb` - `app/services/backup_service.rb`: Minor conflict due to glitch-soc having to handle local-only toots specially. Applied upstream changes and restored the local-only special handling. - `app/views/admin/custom_emojis/index.html.haml`: Minor conflict due to the theming system. - `package.json`: Upstream dependency updated, too close to a glitch-soc-only dependency in the file. - `yarn.lock`: Upstream dependency updated, too close to a glitch-soc-only dependency in the file.
2020-06-06Update dependabot.yml (Fix #13939) (#13990)Shlee
* Update dependabot.yml * Update dependabot.yml
2020-06-05Update Dependabot config (#13939)Shlee
* Delete config.yml * Create dependabot.yml
2019-11-20Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - README.md discarded upstream changes - app/controllers/api/v1/bookmarks_controller.rb finally merged upstream, some code style fixes and slightly changed pagination code - app/controllers/application_controller.rb changed upstream to always return HTML error pages slight conflict caused by theming code - app/models/bookmark.rb finally merged upstream, no real conflict - spec/controllers/api/v1/bookmarks_controller_spec.rb finally merged upstream, slightly changed pagination code
2019-11-13Add config for issue template (#12306)Yamagishi Kazutoshi
2019-10-27Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - README.md - app/helpers/statuses_helper.rb Upstream moved account helpers to their own file, we had extra helpers there, moved too. - app/lib/sanitize_config.rb - app/models/user.rb - app/serializers/initial_state_serializer.rb - config/locales/simple_form.en.yml - spec/lib/sanitize_config_spec.rb
2019-10-26Change stale bot to only touch pull requests over 120 days old (#12217)Eugen Rochko
2019-10-25Create stale.yml (#12207)Eugen Rochko
2019-05-23Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - app/models/account.rb - app/views/settings/profiles/show.html.haml - spec/controllers/api/v1/accounts/credentials_controller_spec.rb Conflicts were due to an increase in account bio length upstream, which is already covered in glitch-soc through `MAX_BIO_CHARS`.
2019-05-23Add sponsor button to GitHub web UI (#10814)Yamagishi Kazutoshi
- https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository
2018-10-22Merge branch 'master' into glitch-soc/merge-upstreamThibaut Girka
Conflicts: - .github/ISSUE_TEMPLATE/bug_report.md Took our version. - CONTRIBUTING.md Updated the embedded copy of upstream's version. - README.md Took our version. - app/policies/status_policy.rb Not a real conflict, took code from both. - app/views/layouts/embedded.html.haml Added upstream's changes (dns-prefetch) and fixed `%body.embed` - app/views/settings/preferences/show.html.haml Reverted some of upstream changes, as we have a page dedicated for flavours and skins. - config/initializers/content_security_policy.rb Kept our version of the CSP. - config/initializers/doorkeeper.rb Not a real conflict, took code from both.
2018-10-16Fix feature request issue templateEugen Rochko
2018-10-16Update issue templates (#8989)Eugen Rochko
* Update issue templates * Update bug_report.md * Update feature_request.md * Update support.md * Update feature_request.md
2018-08-19Adapt github issue template to glitch-socThibaut Girka
We don't have releases, so it don't make sense to mention. On the other hand, a lot of our code is from upstream, so encourage people to check whether it is a bug in glitch-soc or upstream.
2018-05-08Multiple Issue templates (#7402)Yamagishi Kazutoshi
* Multiple Issue templates * Update bug_report.md
2017-12-12Move files for GitHub to .github directory (#5989)Yamagishi Kazutoshi
generated by cgit-pink (git 2.37.1) at 2024-11-18 11:11:06 +0000