Would be great to have some transparency, perhaps a "# of users banned in this repo". That'd be one way to see where the balance of "abuse" lies, with the repo/org or the contributors. In other words, another indicator for health of the community, just like # of stars, forks, contributors, and watchers.
Giving a number of banned users is something that, counterintuitively, is very abuseable. Someone with an axe to grind could pretty easily create a bunch of sockpuppet accounts with the sheer purpose of getting accounts banned and that number inflated, thus giving an appearance of a community being unwelcome.
It seems like more of an indicator of whether the project was involved in some sort of controversy. I don't think you can say anything about a "balance of abuse" just based on the number of users banned.
"fastlane lets you define and run your deployment pipelines for different environments. It helps you unify your app’s release process and automate the whole process. fastlane connects all fastlane tools and third party tools, like CocoaPods and Gradle." directly from the horses mouth https://fastlane.tools/
I'm obviously a fan.
It's a Ruby-based DSL that wraps a collection of small CLI tools to define the entire workflow. It can handle most aspects out-of-box like building, signing, taking a snapshot, pushing, etc. It appears to be extensible too, but I haven't tried that much yet.
We fixed the XSS issue. Having said that, this site is just to demonstrate that you can use any standard web socket client (including the one in your browser); normally you would build the XSS mitigation into the client app if necessary.
What scenario do you have in mind for a "pub-sub pattern using WS"?
It might not be the scenario we were shooting for. The HTTP endpoint was an important requirement. We needed a way to receive HTTP POST calls in an app which wasn't accessible from the web (i.e. no incoming HTTP, but we could make an outbound WS call). Something like Runscope's Passageway (https://www.runscope.com/docs/passageway) would have been our first choice, but it wasn't easy to bake it into the app itself.
Would love to see the API support a POST for creating a new build and passing in the project code (or slug url). This would enable the other git providers (Gitlab, BitBucket, Gogs, etc) and 3rd party services/frameworks (e.g. Factor.io) to provide the integration.
We do have an API that supports triggering builds with a POST request, passing in custom parameters, etc. The bigger issue is that we strive for a really rich integration between us and GitHub. For example, we support their status API, link back to PRs/commits from our build page, etc. It's a lot more than just triggering builds.
We do have support for other services planned, but we are focused on the GitHub experience for now.
I can't speak for others, but I can for Factor.io’s twist... (1) It is Open Source + Hosted + Pro. (2) The recipes ("workflows") can include multiple steps, sequential, and parallel activities; not just limited to if-this-then-that. (3) Workflows are defined programmatically using a Ruby-DSL. (4) You can create both actions and listeners (like events/monitors), though some of the others support this too. (5) It's been around for 2+ years, built with feedback from 100+ dev teams, and used by 1000s.
Have a look at https://factor.io, it is also a deployment engine which can deploy from Github, Bitbucket, etc to your servers (e.g. SCP). It's also much easier to setup. Additionally you can add an intermediate build step with static gen frameworks like Middleman.
Great, now someone's gonna write a static site generator site generator... when does it stop?! There's got to be a list of site/project ideas that people have actually asked for.
Thanks for the mention - we're working on a new version that'll be open-source and more comprehensive (though still limited to open-source static site generators).
as an underlying list, too? Maintaining a listing is pretty tedious with all the SSGs out there. I can set up web hooks and whatever to push to your servers if the listing changes.
