npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

autobit

v5.0.2

Published

bitbucket automation

Downloads

72

Readme

autobit

This is an app to poll a bitbucket branch for PRs. When the PRs are found, it looks for changes from the last poll. If there are changes, it will create a message in a Flowdock flow. If the PR is ready to merge and someone has left the comment "mab", the PR will be merged.

Why autobit?

We were having issues with being ready to merge a PR, but having to remember to come back to it if a build was in progress. Our builds can take 10s of minutes, and often PRs would linger until they were caught at just the right time when builds were complete (builds get spawned for every merge, so there are lots of builds going on). By having a process that polls the PRs looking for the comment "mab", we can let autobit merge when the PR is ready.

Also, we were getting lots of bitbucket emails, and some of us stopped looking at them. Now we can have major PR changes logged to a flow, which is where many people live these days.

Parameters

| Parameter | Alias | Default | Description | | ----------- | ----------- | ------------ |----------- | | --username | -u | - | You have to log in with your credentials to authenticate against bitbucket. you can pass your username here | | --password | -p | - | Bitbucket password - if not specified you'll be prompted | | --branch | -b | - | The branch you want to poll (ex. refs/heads/foo/bar) can be multiple branches (ex. refs/heads/foo/bar refs/heads/bam/baz) | | --flowdockToken | -f | - | The api token to use to authenticate to flowdock | | --bitbucketBaseUrl | -l | - | The base url to your bitbucket instance (ex. https://bitbucket.foo.com/rest/api/1.0) | | --proxyBypass | -y | - | Addresses you don't want going through whatever proxy you have (i have a no_proxy export, but it doesn't seem to get honored by the library i'm using) (ex. foo.com) | | --proxyUrl | -x | '' | The url to your proxy, if any | | --flowName | - | - | The name of the flow to post to (ex. 'Myflow for automation') | | --repository | - | - | The repository part of the path, (ex. projects/foo/repos/bar) | | --intervalSeconds | - | 10 | The number of seconds between polling (defaults to 10) | | --flowdockUsername | - | 'autobit' | The name displayed for flowdock automation messages (defaults to autobit) | | --flowdockBlacklist | - | - | Exclude certain usernames from flowdock messaging |

Installation

Install autobit with npm i -g autobit

Usage

Run autobit from the terminal, ex. autobit -u myusername -b refs/heads/foo/bar -f 2asdfasff232234234234 --bitbucketBaseUrl https://bitbucket.foo.com -flowName 'My automation' -repository projects/foo/repos/bar

Notes

  • If autobit fails due to a 401, authentication failed, the process will exit and an error will be logged to flowdock. This should only happen if your credentials are no longer valid, in which case you'll have to start the process again to enter your password.

  • "mab" is the comment used to tell autobit you want the PR merged as soon as it's able to be merged

  • "cancel" is a comment you can put after a "mab" to tell autobit to ignore the previous "mab"