Skip to content

Commit

Permalink
Merge b9e9dad into b14e07b
Browse files Browse the repository at this point in the history
  • Loading branch information
juwara0 committed Mar 23, 2018
2 parents b14e07b + b9e9dad commit b4949da
Show file tree
Hide file tree
Showing 9 changed files with 17,454 additions and 26 deletions.
107 changes: 107 additions & 0 deletions .github/ISSUE_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@
Are you opening a **BUG REPORT** or a **FEATURE REQUEST / CODE CHANGE**?

There is a section for each below. Please complete the appropriate section and remove the other one.

We realize there is a lot of data requested here. We ask only that you do your best to provide as much information as possible so we can better help you.


# BUG REPORT

* [ ] I have ensured that the issue isn't already reported
* [ ] I have confirmed that the issue is reproducible with the latest released version
* [ ] I have deleted the **FEATURE REQUEST / CODE CHANGE** section

## Summary
* Provide a general summary of the issue in the title above

## Expected Behavior
* What should happen?

## Actual Behavior
* What happens instead of the expected behavior?
* Is something broken, or not behaving as you expected?
* Attach a screenshot or recording as appropriate.

## Possible Solution
* Not obligatory, but suggest a fix/reason for the bug

## Steps to Reproduce
* How would you describe your issue to someone who doesn’t know you or your project?
* Try to write a sequence of steps that anybody can repeat to see the issue.
* Be specific! If the bug cannot be reproduced, your issue may be closed.
* Provide a link to a live example, include code to reproduce, or direct us to any relevant files as applicable
* This guide has some additional good information: https://stackoverflow.com/help/mcve

---

* [ ] Include the contents of your _package.json_ file
* [ ] Steps to reproduce:
1.
2.
3.
4.
...


## Context
* How has this issue affected you? What are you trying to accomplish?
* Providing context helps us come up with a solution that is most useful in the real world.

## Environment

(answer all that are applicable)

* [ ] I am using the latest released version (can check with `npm ls <package-name>`)
* I am using these browsers:
* [ ] Latest Chrome
* [ ] Latest Firefox
* [ ] My version of `Node` is:
* [ ] My version of `npm` is:
* [ ] My OS is:
* [ ] Include the contents of your _package.json_ file




# FEATURE REQUEST / CODE CHANGE

* [ ] I have deleted the **BUG REPORT** section

## Summary
* [ ] Provide a general summary of the requested feature in the title above
* [ ] Provide a one-paragraph explanation of the requested feature:


## Motivation
* Describe the big picture of your feature to communicate why it should be added.
* Why are we doing this?
* What use cases does it support?
* What is the expected outcome?

## Detailed design
This is the bulk of the Feature Request / Code Change.

Explain the design in enough detail for somebody familiar with this addon, the UI Platform ecosystem, and Ember.js to understand, and for somebody familiar with the implementation to implement. This should get into specifics and corner-cases, and include examples of how the feature is used. Any new terminology should be defined here.

## How we teach this

* What names and terminology work best for these concepts and why?
* How should this feature be introduced and taught to existing users?

## Drawbacks

* Why should we ***not*** do this? Please consider the impact...
* ...on teaching this
* ...on the integration of this feature with other existing and planned features
* ...on the impact of the API churn on existing apps
* ...etc.
* There are tradeoffs to choosing any path, please attempt to identify them here.

## Alternatives

* What other designs have been considered? What is the impact of not doing this?
* This section could also include prior art, that is, how other addons or libraries in the same domain have solved this problem.

## Unresolved questions

* Optional, but suggested for first drafts. What parts of the design are still TBD?
70 changes: 65 additions & 5 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,69 @@
### This project uses [semver](semver.org), please check the scope of this pr:
# Overview

- [ ] #none# - documentation fixes and/or test additions
- [ ] #patch# - backwards-compatible bug fix
- [ ] #minor# - adding functionality in a backwards-compatible manner
- [ ] #major# - incompatible API change
## Does this PR close an existing issue?
No PR should be opened without opening an issue first. Any change needs to be discussed before proceeding.

## Summary
Provide a general summary of the issue addressed in the title above

## Issue Number(s)
Which issue(s) does this PR address?

Put `Closes #XXXX` below to auto-close the issue that this PR addresses:

* Closes #

## Screenshots or recordings
Please provide screenshots or recordings if this PR is modifying the visual UI or UX.

## Checklist
* [ ] I have added tests that prove my fix is effective or that my feature works
* [ ] I have evaluated if the _README.md_ documentation needs to be updated
* [ ] I have evaluated if the _/tests/dummy/_ app needs to be modified
* [ ] I have evaluated if DocBlock headers needed to be added or updated
* [ ] I have verified that lint and tests pass locally with my changes
* [ ] If a fork of a dependent package had to be made to address the issue this PR closes:
* [ ] I noted in the fork's _README.md_ the reason the fork was created
* [ ] I have opened an upstream issue detailing what was deficient about the dependency
* [ ] I have opened an upstream PR addressing this deficiency
* [ ] I have opened an issue in this repository to track this PR and schedule the removal of the usage of the fork


# Semver

**This project uses [semver](http://semver.org), please check the scope of this PR:**

- [ ] #none#
- [ ] #patch#
- [ ] #minor#
- [ ] #major#

Examples:
* **NONE**
* _README.md_ changes
* test additions
* changes to files that are not used by a consuming application (_.travis.yml_, _.gitignore_, etc)
* **PATCH**
* backwards-compatible bug fix
* nothing about how to use the code has changed
* nothing about the outcome of the code has changed (though it likely corrected it)
* changes to demo app (_/tests/dummy/_)
* **MINOR**
* adding functionality in a backwards-compatible manner
* nothing about how used to use the code has changed but using it in a new way will do new things
* nothing about the outcome of the code has changed without having to first use it in a new way
* addition of new CSS selectors
* addition of new `ember-hook` selectors
* **MAJOR**
* incompatible API change
* using the code how used to will cease working
* using the code how used to will have a different outcome
* any changes to CSS selector names
* any removal of CSS selectors
* any changes to `ember-hook` selectors
* possibly changes to test helpers (depends on the changes made)
* any changes to the **_dependencies_** entry in the _package.json_ file

# CHANGELOG

Please add a description of your change here, it will be automatically prepended to the `CHANGELOG.md` file.
1 change: 0 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@
/coverage/*
/libpeerconnection.log
npm-debug.log*
package-lock.json
testem.log
coverage.json
.DS_Store
Expand Down
10 changes: 7 additions & 3 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ dist: trusty
language: node_js

node_js:
- '6.11.0'
- '8.1.2'
- 'stable'

addons:
Expand Down Expand Up @@ -32,11 +32,12 @@ matrix:
before_install:
- npm config set spin false
- npm install -g bower
- npm install -g coveralls pr-bumper@^2.0.0
- npm install -g coveralls pr-bumper@^3.7.0 ciena-devops@^1.0.0
- $(npm root -g)/pr-bumper/.travis/maybe-check-scope.sh

install:
- $(npm root -g)/pr-bumper/.travis/maybe-install.sh
- bower install

before_script:
- "export DISPLAY=:99.0"
Expand All @@ -60,9 +61,12 @@ deploy:
on:
all_branches: true
condition: "$EMBER_TRY_SCENARIO = 'ember-default'"
node: '6.11.0'
node: '8.1.2'
tags: true

after_deploy:
- $(npm root -g)/ciena-devops/scripts/slack/incoming-webhooks/send-message.sh

notifications:
slack:
secure: GCEop3ajbWxsx8pRuQjcDoFtUQisHmb99lW1JWXs8Pi1kkkYlk+SYA0oPUr2qt2n2uhicfgDPKlnl3xlpYjstS2KaR0SGLuRjs/B+xPlQN/lHsID3Ir72ohabA88q07RKTgSrjdAG8e7igV4D6N29DYMUWUfdu8/+STFOhIew+JjLHNS+qPHHnYQMLvKoVAF+0NC+geSkOABOip8dvOT/t0ODjs3dIJb1zF4ja2zX2KYLc0JZCXjFjq/bBXMu9qi8MGj9E06ko+IhHHR8vRJ0Ldqg8f70V31raH7jKmFoxkkpGBuA17VWmLz3Zc+8pga2bc9DbTFhQuLEFnc3lbiQuK5mlhRxN491pY0Rt3cRxtYvsX9sVD5YsOF6Fe3TSgl58E7nObIzRSV1lhTJGXV+3fiBNAat3+pGCCIU9bNM0l6ArhrrG0Vm3Fgr/PtsUNtphWgnxfsjWiGbCk4j0hoN/LgHzo7DQx/YW4W1M5OM5NfLJYf6uomV0LLAZYKvKp279XHMSiBYMia/8FtVnWeAb8Qb+fTpOV3ixP1VaxYSgfmSzEslK8dg95HTsXyUQySNV8AG7PlzAF4krF015ler6h2KszfUMHsF4+qxxAuKQhIfP8cgQf4caChW2EmbcNcZ7viURVtYpjJH8PBZsIG7cuqHWExdAlztCDJFtCX9Jc=
6 changes: 3 additions & 3 deletions .travis/maybe-bump-version.sh
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
#!/bin/bash

if [ "$TRAVIS_NODE_VERSION" != "6.11.0" ]
if [[ ! "${PUBLISH_NODE_VERSION:-8.1.2}" =~ ^$TRAVIS_NODE_VERSION ]]
then
echo "Skipping version bump for TRAVIS_NODE_VERSION ${TRAVIS_NODE_VERSION}"
echo "Skipping pr-bumper bump step for TRAVIS_NODE_VERSION [${TRAVIS_NODE_VERSION}]"
exit 0
fi

if [ "$EMBER_TRY_SCENARIO" != "ember-default" ]
then
echo "Skipping version bump for EMBER_TRY_SCENARIO ${EMBER_TRY_SCENARIO}"
echo "Skipping pr-bumper bump step for EMBER_TRY_SCENARIO [${EMBER_TRY_SCENARIO}]"
exit 0
fi

Expand Down
8 changes: 4 additions & 4 deletions .travis/maybe-publish-coverage.sh
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,19 @@ source $(npm root -g)/pr-bumper/.travis/is-bump-commit.sh

if isBumpCommit
then
echo "Skipping coverage publish for version bump commit"
echo "Skipping pr-bumper coverage publish step for version bump commit"
exit 0
fi

if [ "$TRAVIS_NODE_VERSION" != "6.11.0" ]
if [[ ! "${PUBLISH_NODE_VERSION:-8.1.2}" =~ ^$TRAVIS_NODE_VERSION ]]
then
echo "Skipping coverage publish for TRAVIS_NODE_VERSION ${TRAVIS_NODE_VERSION}"
echo "Skipping pr-bumper coverage publish step for TRAVIS_NODE_VERSION [${TRAVIS_NODE_VERSION}]"
exit 0
fi

if [ "$EMBER_TRY_SCENARIO" != "ember-default" ]
then
echo "Skipping coverage publish for EMBER_TRY_SCENARIO ${EMBER_TRY_SCENARIO}"
echo "Skipping pr-bumper coverage publish step for EMBER_TRY_SCENARIO [${EMBER_TRY_SCENARIO}]"
exit 0
fi

Expand Down
6 changes: 3 additions & 3 deletions .travis/maybe-publish-gh-pages.sh
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ source $(npm root -g)/pr-bumper/.travis/is-bump-commit.sh

if isBumpCommit
then
echo "Skipping gh-pages publish for version bump commit"
echo "Skipping pr-bumper gh-pages publish step for version bump commit"
exit 0
fi

Expand All @@ -14,7 +14,7 @@ TMP_GH_PAGES_DIR=.gh-pages-demo
# We only want to deploy to gh-pages from "master"
if [ "${TRAVIS_BRANCH}" != "master" ]
then
echo "Skipping gh-pages publish for branch ${TRAVIS_BRANCH}"
echo "Skipping pr-bumper gh-pages publish step for branch [${TRAVIS_BRANCH}]"
exit 0
fi

Expand All @@ -25,5 +25,5 @@ git checkout gh-pages
git rm -rf *
cp -r ../dist/* .
git add --all
git commit -m "[ci skip] Automated gh-pages commit of ${VERSION}"
git commit -m "[pr-bumper] Automated gh-pages commit of [${VERSION}]"
git push origin gh-pages > /dev/null 2>&1

0 comments on commit b4949da

Please sign in to comment.