Skip to content

Commit

Permalink
1.1.0-preview.12
Browse files Browse the repository at this point in the history
# [1.1.0-preview.12](v1.1.0-preview.11...v1.1.0-preview.12) (2020-03-07)

### Bug Fixes

* console log is a little chatty [#82](#82) ([a632d7f](a632d7f))
* releases wrongly being flagged as preview ([a32069e](a32069e)), closes [#83](#83)

### Features

* add keywords to package.json ([c0ee69e](c0ee69e))
  • Loading branch information
semantic-release-bot committed Mar 7, 2020
1 parent b0032f7 commit aa9f6ea
Show file tree
Hide file tree
Showing 9 changed files with 220 additions and 84 deletions.
13 changes: 13 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
# [1.1.0-preview.12](https://github.com/mob-sakai/UpmGitExtension/compare/v1.1.0-preview.11...v1.1.0-preview.12) (2020-03-07)


### Bug Fixes

* console log is a little chatty [#82](https://github.com/mob-sakai/UpmGitExtension/issues/82) ([a632d7f](https://github.com/mob-sakai/UpmGitExtension/commit/a632d7fc2f560967ca982b0f3b68334214f83ad5))
* releases wrongly being flagged as "preview" ([a32069e](https://github.com/mob-sakai/UpmGitExtension/commit/a32069efa78c028ebc1ac3b0daa2d86f3cd7ff58)), closes [#83](https://github.com/mob-sakai/UpmGitExtension/issues/83)


### Features

* add keywords to package.json ([c0ee69e](https://github.com/mob-sakai/UpmGitExtension/commit/c0ee69ea21ec08075396a83420b8d1c8f3457ac9))

# [1.1.0-preview.11](https://github.com/mob-sakai/UpmGitExtension/compare/v1.1.0-preview.10...v1.1.0-preview.11) (2020-02-27)


Expand Down
84 changes: 84 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
7 changes: 7 additions & 0 deletions CODE_OF_CONDUCT.md.meta

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

30 changes: 30 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Contributing

## How to Contribute

#### Code of Conduct

This repository has adopted the Contributor Covenant as it's
Code of Conduct. It is expected that participants adhere to it.

#### Proposing a Change

If you are unsure about whether or not a change is desired,
you can create an issue. This is useful because it creates
the possibility for a discussion that's visible to everyone.

When fixing a bug it is fine to submit a pull request right away.

#### Sending a Pull Request

Steps to be performed to submit a pull request:

1. Fork the repository and create your branch from `develop`.
2. If you have fixed a bug or added code that should be tested, add tests.
3. Click `Window > Generals > Test Runner` to test
4. Commit with a massage based on [Angular Commit Message Conventions](https://gist.github.com/stephenparish/9941e89d80e2bc58a153).
5. Fill out the description, link any related issues and submit your pull request.

#### License

By contributing to this repository, you agree that your contributions will be licensed under its MIT license.
7 changes: 7 additions & 0 deletions CONTRIBUTING.md.meta

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,6 @@ static void OnResultCreated(string file)

var text = File.ReadAllText(file, System.Text.Encoding.UTF8);
File.Delete(file);
UnityEngine.Debug.Log($"{kHeader} OnResultCreated {file}:\n{text}");

try
{
Expand Down
2 changes: 1 addition & 1 deletion Editor/Coffee.UpmGitExtension/InternalBridge.cs
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,7 @@ internal static UpmPackageVersion ToPackageVersion(this AvailableVersion self, U

// Update tag.
PackageTag tag = PackageTag.Git | PackageTag.Installable | PackageTag.Removable;
if (semver.Major == 0 || string.IsNullOrEmpty(semver.Prerelease))
if (semver.Major == 0 || !string.IsNullOrEmpty(semver.Prerelease))
tag |= PackageTag.Preview;
else if (semver.IsRelease())
tag |= PackageTag.Release;
Expand Down
Loading

0 comments on commit aa9f6ea

Please sign in to comment.