Closed elbrujohalcon closed 3 years ago
I'm OK with both.
Is there an easy way to copy between repo.s?
Also, when updating/removing the Wiki we should make sure the appropriate info. makes its way to README.md
.
I'm not sure if there is an easy way… My plan was to do it The Hard Way:tm:
I'm OK with Discussions and making this the first discussion 😄
elvis_core
[3] [4](I wonder how difficult it would be to make elvis
into a GitHub Action)
[1] I didn't "port" - Implement more rules that enforce additional Erlang guidelines.
since this is a constant work in progress.
[2] I'll port the Benefits to README.md
: e0aeda4
[3] I left Rules out, since this is basically part of elvis_core
[4] I left Customization out, since I believe it's not important as-is
It should be possible to transfer an open issue to another repository, but I don't think I have permissions for it, so leave it up to you guys.
Yeah… My plan is to work on the movement of tickets and stuff at some point during my vacations. That is… in 2 weeks.
What else could I do to help here?
What else could I do to help here?
Wait... I guess 😜
Done.
El hombre.
@jfacorro / @paulo-ferraz-oliveira : What do you think about…
elvis_core
repo?elvis_core
?