<commit_before>## Publishing a Package

This guide will show you how to publish a package or theme to the
[atom.io][atomio] package registry.

Publishing a package allows other people to install it and use it in Atom.  It
is a great way to share what you've made and get feedback and contributions from
others.

This guide assumes your package's name is `my-package` but you should pick a
better name.

### Install apm

The `apm` command line utility that ships with Atom supports publishing packages
to the atom.io registry.

Check that you have `apm` installed by running the following command in your
terminal:

```sh
apm help publish
```

You should see a message print out with details about the `apm publish` command.

If you do not, launch Atom and run the _Atom > Install Shell Commmands_ menu
to install the `apm` and `atom` commands.

### Prepare Your Package

If you've followed the steps in the [your first package][your-first-package]
doc then you should be ready to publish and you can skip to the next step.

If not, there are a few things you should check before publishing:

  * Your *package.json* file contains the accurate `name`, `description`,
    and `repository` information.
  * Your *package.json* file has a version field of `0.0.0`.
  * Your *package.json* file has an `engines` field that contains an entry
    for Atom such as: `"engines": {"atom": ">=0.50.0"}`.
  * Your package is stored in a git repository that is hosted on
    [GitHub][github].
  * Your package has a `README.md` file at the root.
  
### Publish Your Package

One last thing to check before publishing is that a package with the same
name hasn't already been published to atom.io.  You can do so by visiting
`http://atom.io/packages/my-package` to see if the package already exists.
If it does, update your package's name to something that is available.

Run the following commands to publish your package (this assumes your package
is located at `~/github/my-package`).

```sh
cd ~/github/my-package
apm publish minor
```

If this is the first time you are publishing, the `apm publish` command may
prompt you for your GitHub] username and password. This is required to publish
and you only need to enter this information the first time you publish. The
credentials are stored securely in your [keychain][keychain] once you login.

The `minor` option to the publish command tells apm to increment the second
digit of the version before publishing so the published version will be `0.1.0`.
You could have run `apm publish major` to publish a `1.0.0` version  but since
this is your first version it is better to start with minor release. You can
read more about semantic versioning [here][semver].
<commit_msg>Remove stray ]<commit_after>## Publishing a Package

This guide will show you how to publish a package or theme to the
[atom.io][atomio] package registry.

Publishing a package allows other people to install it and use it in Atom.  It
is a great way to share what you've made and get feedback and contributions from
others.

This guide assumes your package's name is `my-package` but you should pick a
better name.

### Install apm

The `apm` command line utility that ships with Atom supports publishing packages
to the atom.io registry.

Check that you have `apm` installed by running the following command in your
terminal:

```sh
apm help publish
```

You should see a message print out with details about the `apm publish` command.

If you do not, launch Atom and run the _Atom > Install Shell Commmands_ menu
to install the `apm` and `atom` commands.

### Prepare Your Package

If you've followed the steps in the [your first package][your-first-package]
doc then you should be ready to publish and you can skip to the next step.

If not, there are a few things you should check before publishing:

  * Your *package.json* file contains the accurate `name`, `description`,
    and `repository` information.
  * Your *package.json* file has a version field of `0.0.0`.
  * Your *package.json* file has an `engines` field that contains an entry
    for Atom such as: `"engines": {"atom": ">=0.50.0"}`.
  * Your package is stored in a git repository that is hosted on
    [GitHub][github].
  * Your package has a `README.md` file at the root.
  
### Publish Your Package

One last thing to check before publishing is that a package with the same
name hasn't already been published to atom.io.  You can do so by visiting
`http://atom.io/packages/my-package` to see if the package already exists.
If it does, update your package's name to something that is available.

Run the following commands to publish your package (this assumes your package
is located at `~/github/my-package`).

```sh
cd ~/github/my-package
apm publish minor
```

If this is the first time you are publishing, the `apm publish` command may
prompt you for your GitHub username and password. This is required to publish
and you only need to enter this information the first time you publish. The
credentials are stored securely in your [keychain][keychain] once you login.

The `minor` option to the publish command tells apm to increment the second
digit of the version before publishing so the published version will be `0.1.0`.
You could have run `apm publish major` to publish a `1.0.0` version  but since
this is your first version it is better to start with minor release. You can
read more about semantic versioning [here][semver].

{'fraction_non_alphanumeric': 0.06747787610619468, 'fraction_numerical': 0.004793510324483776, 'mean_word_length': 4.074836295603368, 'pattern_counts': {'":': 4, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3193267', 'n_tokens_mistral': 1483, 'n_tokens_neox': 1439, 'n_words': 848}