by kmf on 12/19/19, 4:14 PM with 129 comments
by ccleve on 12/19/19, 6:55 PM
Github documentation is a disaster. They leave out critical parts. They don't provide examples. Everything they write is terse, confusing, and incomplete.
They have short little articles on how to do things, and for each sub-task they have a link to docs somewhere else. This would be fine, except the links don't point to anything useful.
To give an example: they say you can use the Github API to talk to Github Packages, but the link goes to their generic GraphQL documentation. They don't point to any reference material on the actual calls to the packages service. If it exists, I can't find it.
If you go to the main page in your account for Github Packages, it says that all you have to do is this:
mvn deploy -Dregistry=https://maven.pkg.github.com/mycompany -Dtoken=GH_TOKEN
That is just straight-out wrong. It does not work.
Seriously, Github, you need to fire your documentation team and hire some people who know how to write. Perhaps you should hire people who have actually used your tools to write the docs. Or just provide some freakin' working examples.
by pm90 on 12/19/19, 5:21 PM
by kureikain on 12/19/19, 7:02 PM
I don't know why they didn't allow us to use any docker image we want so we don't have to waste time to use actions to install dependencies...Eg, if your app depend on both Go, Ruby, Node at build time you will need:
https://github.com/actions/setup-go https://github.com/actions/setup-node https://github.com/actions/setup-ruby
I much prefer CircleCI way
by keyP on 12/19/19, 8:05 PM
by ShakataGaNai on 12/20/19, 3:29 AM
There are a lot of cool examples demo'ing some nifty stuff, but I'd like to see a lot of very basic examples first. The sort of thing anyone could/would copy into their project and use, then later learn how to make it fancy.
by itcrowd on 12/19/19, 5:01 PM
by kenver on 12/19/19, 9:41 PM
The process was mostly just changing out a Jenkins file to the GitHub yml and sorting a few issues that cropped up.
by pavlov on 12/19/19, 7:46 PM
This happened already with VS Code vs. Github's Atom editor whose development has ceased earlier this year. (Not that I ever was a huge fan of Atom, but its discontinuation is a direct result of the Microsoft acquisition.)
by amdelamar on 12/19/19, 11:08 PM
name: master-pull-request
on:
pull_request:
branches:
- master
jobs:
test:
name: run tests
runs-on: ubuntu-18.04
steps:
- uses: actions/checkout@v1
- name: Run gradle test
run: |
./gradlew test
kind: pipeline
name: default
steps:
- name: run tests
image: openjdk:8-jdk-slim # Docker images!
commands:
- ./gradlew testby engineeroncall on 12/20/19, 7:14 AM
Most of the actions were pre-existing Makefile targets used during the bootstrap process anyway, so the YAML config was fairly lightweight.
Echoing the other comments in the thread, the docs did feel a bit sparse when I last poked around (this was back when Actions was still in beta).
by louib on 12/19/19, 6:42 PM
That being said, there was only Ubuntu images for the Linux builds, and I'm not aware of a way to run custom containers at the moment.
by pyr0hu on 12/20/19, 6:53 AM
Otherwise it could be a good product, and I'd really like if I could manage the repos and the CI from one unified place
by k__ on 12/19/19, 8:46 PM
by darkwater on 12/20/19, 11:27 AM
by vageli on 12/21/19, 4:32 PM
by karaokeyoga on 12/20/19, 12:54 AM
by NieDzejkob on 12/19/19, 5:41 PM