A stated design goal of is to never make you push weird commits just for the sake of the CI. That means using `git push -o skip-ci` instead of putting `[skip ci]` in your commit message, or letting you paste build manifests into the website to test them instead of pushing a bunch of test commits to see if your CI config works.

(Repeating comment from a thread with a locked participant)

@sir And this is how I learned that Mastodon has privacy settings, and mine were set to "followers-only" 😬

any support for external/remote builds with APIs to feed results in?

@sir So I always assumed that your [skip ci] was just an example of what bad ui could be. At least I thought until I scrolled through the history of this file:

This resulted in me searching for this post again. Who ever thought this was a good idea?

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!