Closed eniovalo closed 4 years ago
It's a good point. We can configure the travis-ci and the goreportcard. btw, ours is A+ https://goreportcard.com/report/github.com/bancodobrasil/stop-analyzing-api
Nice.!
Could we offer this issue to Rafamarts, at #12? Including the go test
feature and the travis-ci thing.
What do you think?
@tiagostutz , I think It's ok. 🙂
It's a good point. We can configure the travis-ci and the goreportcard. btw, ours is A+ https://goreportcard.com/report/github.com/bancodobrasil/stop-analyzing-api
@zamariola , I didn't know this site, it is really nice to see the reports. Thanks. 🙂
Hi guys,
Please, assign to me. I can work on that..
Thank you!
Nice! Assigned to you, @rafamarts!! Go for it.!
I'd like to help with this issue. Can you assign it to me?
Done! Go for it @paulo-vieira-centeno !!
@rafamarts I assigned to @paulo-vieira-centeno and we will work on another issue soon, ok? Thanks!!
@tiagostutz , I was thinking in writing a bash script that performs some of the steps described in README.md file, except for the steps related to the build of the API. These steps would be done in the host machine, so it would make it easier to start developing/testing the API locally. We could also setup the githooks as one of these steps. What do you think about?
Hi @paulo-vieira-centeno !
Sounds good to me! Please, go ahead. 🚀
@tiagostutz , I've already done my local changes in a local branch. I tried to push that branch to github, but got a '403 forbidden'. Can you give me the appropriate permissions to be able to push my branch to the repository?
Thanks for the instructions, @eniovalo
@paulo-vieira-centeno , you're welcome. 🙂
Hi,
We could configure to run
go test
on all project before each commit to validate if the changings break anything. Or if tests are too slow, we could display a console log after commit to remember to rungo test
before push. =]What do you think?