Comments (10)
- Yeah, I guess it's obvious that it would be a graphql parser when it is in graphql org. :)
- Good! We can use that. It would be also good if you sign up with that account for https://coveralls.io/ so we can also publish code coverage. For publishing I would need an encrypted api key.
- Good, for that I would only need encrypted api key for appveyor.yml file (https://ci.appveyor.com/tools/encrypt) so I can publish packages within the build process.
- Nothing special there. Or not anything that can't be done within appveyor.yml file. But I will have to try it out. I would only need those two API keys.
Another thing would be publishing to official NuGet. For that do you propose using the graphql-dotnet-ci account or perhaps one of our accounts?
from parser.
- coveralls: OOHuk90+WRWFPhXeTIqUZGigsmFg0xuqkevpunO4ZL4D71LNJH/Qhl0g5gV+Y8Xn
I have been using my personal account for Nuget, though looks like you can add multiple people to a Nuget. I can sign up the graphql-dotnet-ci account to Nuget.org and we can do both if that works for you.
Working on figuring out the myget situation.
from parser.
MyGet
- token: +l1vfBMajn1WfmXkQ2LdILKxK4fQ5AHSnnU1kf11Bn1xRGUOTCdPhLwHx232piEn
- feed: https://www.myget.org/F/graphql-dotnet/api/v3/index.json
- publish: https://www.myget.org/F/graphql-dotnet/api/v2/package
from parser.
Changed the token for MyGet
from parser.
Perfect! I have some personal matters that I have to attend now, but once I'm back at my PC I'll start implementing CI and adding some nice readme file. It seems that I have eveyrthing I need for now. 👍
About that nuget thing. If you add the package with your existing account and give me rights for being able to deploy it, that works for me as well. I'll connect it to the appveyor build process.
The flow would be: When you push a commit to the master branch with a version tag, it will generate a new package and deploy it to nuget.
Deployment to myget as opposed to deployment to nuget would work on every commit. No version tag needed.
from parser.
Sounds good to me. I think we should be able to use GraphQL-Parser
as the NuGet name.
from parser.
- CI through AppVeyor
- Code coverage
- MyGet package after every build
- NuGet package GraphQL-Parser is there and I sent you an invite for ownership. As it seems there is no real difference in who creates the package as every owner can do pretty much anything.
- All badges in place
- Readme with some examples
- Deploys from CI to Nuget + versioning
Initially I published some packages with a wrong name to that MyGet feed. So just to have it clean I would like to ask you to delete it afterwards. The wrong package is GraphQLParser. Now it creates and publishes packages under name: GraphQL-Parser.
Also after you accept the ownership of the NuGet package, then I'd like to ask you for another encrypted token which would be for the API key so I can connect finish up auto deploys to NuGet.
After this I believe it's all from the initial setup. :)
Thanks!
from parser.
Awesome! I'm traveling today though should be able to get to that tonight.
from parser.
Nuget: ZWTuZ9DB3Svu+HDrn4u9hQ0Q9bpXb/waywJplGWDdncs2f2dY3jAdwLvNtNES7qP
Got the other package deleted.
from parser.
Closing as this is all setup.
from parser.
Related Issues (20)
- Add advanced SDLWriter tests for descriptions and comments HOT 2
- Use string.GetHashCode in ROM HOT 6
- Consider to split GraphQLBooleanValue into two classes for true and false
- Ensure October spec compliance before v8 release and publish release
- Optimize comments and block strings
- Add SDLPrinterOptions.Sorted property HOT 7
- Don't track branch coverage for Debug.Assert HOT 4
- Publish v8.1.0 release HOT 1
- Fix readme on Nuget
- SDLPrinter.Print in addition to SDLPrinter.PrintAsync HOT 8
- Strange formatting of input types with descriptions HOT 16
- More Parse methods HOT 5
- Revise AST constructors
- Add tests to increase code coverage up to 100%
- 9.0.1 formatting - lost indentation of arguments (fine in 8.x) HOT 4
- All literals should have proper indentation in case of preceding comments
- Inconsistent formatting of arguments HOT 16
- Suggested feature: default AST visitor context
- Fix broken indentation
- There's an extra space here also, between `...` and `@skip`.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from parser.