Skip to content

chore(ci): adding appveyor configuration. #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 4, 2016
Merged

Conversation

hansl
Copy link
Contributor

@hansl hansl commented Mar 4, 2016

No description provided.

@hansl hansl force-pushed the appveyor branch 2 times, most recently from 0f5baf5 to b7c6980 Compare March 4, 2016 17:22
@@ -0,0 +1,14 @@
environment:
matrix:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove this line

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -0,0 +1,14 @@
environment:
matrix:
- nodejs_version: "5.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and fix this to be without - prefix

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@jkuri
Copy link
Contributor

jkuri commented Mar 4, 2016

lgtm, lets see if it will be included automatically in "getting green".

@hansl
Copy link
Contributor Author

hansl commented Mar 4, 2016

It won't :) That's why I'm spending some time on it.

@hansl hansl merged commit 9759090 into angular:master Mar 4, 2016
@hansl hansl deleted the appveyor branch March 4, 2016 17:25
This was referenced Mar 10, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants