Deploying each new version of your application is the heart of how Now is used. All iterations will always be accessible for use.
When working on projects for an extended period, the list of these iterated deployments builds up.
Today, we are happy to introduce a new way to discern deployments with tagged metadata.
Starting with version 11.5.0 (and 12.0.0-canary.91 for users on the canary channel), you can attach metadata using the new --meta flag (the shorthand is -m).
For example, this is how you can attach a key named foo with a value of bar when deploying:
now -m foo=bar

Adding multiple metadata keys with their values.

Next, you can filter your deployments by passing that same argument to the now ls command:
now ls -m foo=bar

Listing deployments with a metadata key and an associated value.

As you might have already noticed, this solves the problem of having too many deployments and not knowing how to find the right one in that mess.
Should you want to attach multiple of those key-value pairs to a deployment, however, you can do so by passing multiple instances of the -m argument:
now -m foo=bar -m key=value

Adding multiple metadata keys with their values.

You can attach up to 100 of those key-value pairs to a single deployment.
In turn, you can then also append these arguments to now ls when trying to find the deployment again:
now ls -m foo=bar -m key=value

Listing deployments tagged with the keys of foo and key, and their associated values.

By default, every deployment created with Now for GitHub automatically receives a set of metadata that will allow you to filter by any of the information Git provides you with.
Here is an example of how the metadata could look like (the commit is located here):
githubDeployment = "1",
githubOrg = "zeit",
githubRepo = "docs",
githubCommitOrg = "PaulKinlan",
githubCommitRepo = "docs",
githubCommitRef = "patch-1",
githubCommitSha = "fd60bb07ed7fc6849371d8fd850d9c5f7958c8e9",
githubCommitMessage = "Changing "false" to a boolean on github config",
githubCommitAuthorLogin = "PaulKinlan",
githubCommitAuthorName = "Paul Kinlan"
Thanks to the help of metadata, we are now able to provide you with a much more insightful event list on the dashboard available on our website.
Before this change, you were only able to see the deployment URL and the creator used to always be the owner of the team you were a part of.
Thanks to metadata, all of this changes now:
As you can see, the correct authors of deployments generated by commits are now shown. In addition, every deployment created through GitHub receives a special icon.
Thanks to our GitHub integration, anyone with access to your repositories can trigger a deployment by pushing a commit or creating a pull request.
The contributor does not even need to be a member of your team on Now.
Even people outside of your team can trigger deployments, as long as they are capable of creating pull requests or commits.
Before this change, the dashboard was not rendering this information. But thanks to metadata support, you can now see those deployments along your regular ones.
This could even be used as a management tool, allowing your team to visualize what certain team members are building and try the results out right away by clicking on the deployment URL – all in a single place.