build work

.changeset/README.md

@@ -0,0 +1,36 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@atlaskit/build-releases`, a build tool that works with `bolt` to help you release components from a mono-repository. You can find the full documentation for it [here](https://www.npmjs.com/package/@atlaskit/build-releases)
+
+To help you get started though, here are some things you should know about this folder:
+
+## Changesets are automatically generated
+
+Changesets are generated by the `build-releases changeset` command, though it may have been given a new name within your repository. As long as you are following a changeset release flow, you shouldn't have any problems.
+
+## Each changeset is its own folder
+
+We use hashes by default for these folder names to avoid collisions when generating them, but there's no harm that will come from renaming them.
+
+## Changesets are automatically removed
+
+When `build-releases version` or equivalent command is run, all the changeset folders are removed. This is so we only ever use a changeset once. This makes this a very bad place to store any other information.
+
+## Changesets come in two parts
+
+You should treat these parts quite differently:
+
+- `changes.md` is a file you should feel free to edit as much as you want. It will be appended to your changelog when you next run your version command.
+- `changes.json` is a file that includes information about releases, what should be versioned by the version command. We strongly recommend against editing this directly, as you may make a new changeset that puts your bolt repository into an invalid state.
+
+## I want to edit the information in a `changes.json` - how do I do it safely?
+
+The best option is to make a new changeset using the changeset command, copy over the `changes.md`, then delete the old changeset.
+
+## Can I rename the folder for my changeset?
+
+Absolutely! We need unique hashes to make changesets play nicely with git, but changing your folder from our hash to your own name isn't going to cause any problems.
+
+## Can I manually delete changesets?
+
+You can, but you should be aware this will remove the intent to release communicated by the changeset, and should be done with caution.

.changeset/config.js

@@ -0,0 +1,48 @@
+const getLinkMD = commit =>
+  `[${commit}](https://bitbucket.org/atlassian/atlaskit-mk-2/commits/${commit})`;
+
+const getReleaseLine = async (changeset, versionType) => {
+  const indentedSummary = changeset.summary
+    .split('\n')
+    .map(l => `  ${l}`.trimRight())
+    .join('\n');
+
+  return `- [${versionType}] ${getLinkMD(
+    changeset.commit,
+  )}:\n\n${indentedSummary}`;
+};
+
+const getDependencyReleaseLine = async (changesets, dependenciesUpdated) => {
+  if (dependenciesUpdated.length === 0) return '';
+
+  const changesetLinks = changesets.map(
+    changeset => `- Updated dependencies ${getLinkMD(changeset.commit)}:`,
+  );
+
+  const updatedDepenenciesList = dependenciesUpdated.map(
+    dependency => `  - ${dependency.name}@${dependency.version}`,
+  );
+
+  return [...changesetLinks, ...updatedDepenenciesList].join('\n');
+};
+
+const changesetOptions = {
+  commit: true,
+};
+
+const versionOptions = {
+  commit: true,
+  skipCI: true,
+  getReleaseLine,
+  getDependencyReleaseLine,
+};
+
+const publishOptions = {
+  public: true,
+};
+
+module.exports = {
+  versionOptions,
+  changesetOptions,
+  publishOptions,
+};

.editorconfig

@@ -0,0 +1,13 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

.eslintignore

@@ -0,0 +1,39 @@
+# Follows https://git-scm.com/docs/gitignore#_pattern_format
+# In particular, if the pattern has a slash that isn't trailing, it becomes relative to the current file
+# So use ** in those cases
+node_modules
+coverage
+dist
+flow-typed
+.yarn
+
+# the docs template
+docs/templates/**
+
+# the core icon package
+packages/core/icon/glyph/**
+packages/core/icon/cjs/**
+packages/core/icon/utils/**
+
+# the icon icon-file-type package
+packages/core/icon-file-type/glyph/**
+packages/core/icon-file-type/cjs/**
+packages/core/icon-file-type/utils/**
+
+# the icon icon-object package
+packages/core/icon-object/glyph/**
+packages/core/icon-object/cjs/**
+packages/core/icon-object/utils/**
+packages/bitbucket/codemod-util-shared-styles-to-theme/__fixtures__
+
+# the icon icon-priority package
+packages/core/icon-priority/glyph/**
+packages/core/icon-priority/cjs/**
+packages/core/icon-priority/utils/**
+
+# flow tests
+packages/**/__tests__/flow/
+
+# tmp
+build
+website