![]() While the principles behind the 24 hours of innovation have remained the same since the beginning, the framework for ShipIt has evolved in lock-step with Atlassian. Importantly, the evolution of ShipIt has not been limited only to the number of participants and locations. Now, we have nearly 4,000 Atlassians participating across more than 20 cities in at least 11 countries. Our first ShipIt included 14 developers in one location. ![]() While the principles behind ShipIt have remained the same since the beginning, the scale has changed significantly. We all have so much to learn from each other. Collaborate and have fun: Use your ShipIt as a way to get to know and work with different people at your company. Encourage people to go after big ideas, even if they’re not sure how it will turn out. Embrace failure: The beauty of going after big ideas and big impact in such a short period of time is that failure is a great way to learn. Invite people to create “non technical” projects, and award the best one.Ģ. Be conscious of designing an event that includes everyone. Innovation is for EVERYONE: While “hackathons” ring true with engineers, the term itself can be intimidating for non-technical folks. You should never really have to run auto yourself, the CI will do that on each build!Īll you have to know is what the labels are and when to use them.Inspired to unleash the potential of your team? Here are three rules to jumpstart your own ShipIt:ġ. No longer worry what tag to publish to or what version. Now that you know all of the above, you have all you need to release every build as the correct version. export PATH= $(npm bin) :$PATH if auto label -pr $PR_NUMBER -exists Visual then npm run test:visual fi export PATH= $(npm bin) :$PATH if auto label -pr $PR_NUMBER -exists Visual then npm run test:visual fi the following will only run the test:visual script when the PR has has the Visual label. ![]() Using that information you can choose to run extra CI jobs.įor example. This command will return the labels for a PR. Arbitrary labelsĪuto doesn't use any extra labels, but you can use whatever labels to power more automated workflows with auto label. You can configure more changelog sections, read more here. Or use them on their own to just create a patch release. Add them to PRs with release labels to override what changelog section the changes display in. These labels can be used to make your changelogs more expressive.
0 Comments
Leave a Reply. |