eleanorakh

• Keep eyes peeled for potential of threading!
• Machine learning is coming.
• Slack has single chanel collaboration with external agencies - could potentially be used for authors? Although I envision that becoming complicated
• Don't be afraid to police chanels. If something seems off-topic for a chanel, direct the user to a more appropriate discussion place (courteously!). Lopp calls this :racoon:ing
• Devs release to web 40 times per day
• They suggest a 'no internal email' day to get staff on board
• Staff need to understand why we use slack before they begin to use it...the more onboarded onto slack earlier means as the company grows theres a better position to handle future change
• Words like: 'transparent behaviours', 'key champions to guide people'
• Questions:
• What's our active daily user engagement?

eleanorakh

Here's to history: programming through archaeology, RailsConf 2018

Commits

• https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
• https://github.com/erlang/otp/wiki/writing-good-commit-messages
• http://who-t.blogspot.com.au/2009/12/on-commit-messages.html
• https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53
• https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages

eleanorakh

diff --git a/environment-hook.bash b/environment-hook.bash
index f5d2649..8d664b8 100644
--- a/environment-hook.bash
+++ b/environment-hook.bash
@@ -1,4 +1,4 @@
-if [[ "${BUILDKITE_LABEL:-}" != ":pipeline:" ]]; then
+if [[ "${BUILDKITE_STEP_IDENTIFIER:-}" != "pipeline-upload" ]]; then
   echo "--- :git: Getting scala-common tests"
   git clone git@github.com:redacted/redacted.git