At Pixelsmith, we have the pleasure of working remotely. Even though that can be a huge benefit to the employees and company overall, there are some drawbacks as well. Namely it’s a lot harder to randomly catch up with co-workers on their latest viewings of Stranger Things. One way to help combat with this, is to stay connected. It’s important to make sure communication is open for work and non-work issues. There are a few services that our team have benefited from using.
Slack is one of them. It gives us the flexibility to keep conversations grouped by a project and still connect with video and screen sharing as needed. It takes the guess work out of which comment applies to which project.
We also use Springloops as our git repo and deployment service. You will hear more about the benefits within Springloops that our team has found, further in this post.
Sifter is our bug tracker. Simple, straightforward checks and balances to ensure the work is being done right and well. It also let’s us route through the proper team members whether they are internal or client facing.
As developers, it’s in our nature to take this a step further and push to connect services through APIs. Our wheels were spinning the other day (as they naturally do when you have to complete a task over 100 times). We realized that all 3 services have integration tools available to them. Starting with the first two, Springloops and Slack.
Step 1. Tie into Springloops web hook.
We thought it’d be great if everyone on the team could be aware of the edits currently going on within each project. Through some work within the integrations on Slack and Springloops, we were able to enable our git repo to post a message and any other relevant information any time something was committed to the corresponding slack channel/project it pertains to. We did this by going into the deployment section of our project within Springloops, where we are given the option to add a web hook (along with other various options to select).
Step 2. Receive the web hook and format a message.
We then took the information sent from Springloops and tried to make sense of what to do with it. Various information includes: who posted it, what the project and branch names were as well as other helpful metadata to format a message.
Step 3. Post message to Slack
Finally, after we formatted a message, we posted that message to slack. This now allows the entire team to see the latest changes/commits to certain projects and what branch it was completed in.
Our next goal is to incorporate Sifter into the same workflow. At the time of writing this post we are able to parse out a ticket ID from a commit message, but Sifter only offers a way to create new tickets, no option to update existing tickets.
Hopefully some of these tips will help your team to either stay connected or ideate new ways to help your workflow. What processes does your team utilize to save yourself from repeating mundane everyday tasks? Let us know @pixelsmith_co.