Skip to content
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

[META] Reorganize issues / projects / wikis #553

Closed
2 tasks done
elbrujohalcon opened this issue Nov 26, 2020 · 12 comments
Closed
2 tasks done

[META] Reorganize issues / projects / wikis #553

elbrujohalcon opened this issue Nov 26, 2020 · 12 comments
Assignees

Comments

@elbrujohalcon
Copy link
Member

elbrujohalcon commented Nov 26, 2020

@jfacorro / @paulo-ferraz-oliveira : What do you think about…

  • Copying the elvis-core issues to the elvis_core repo?
  • Removing the wiki from this project? Or, at least, leaving just a link to the one in elvis_core?
@paulo-ferraz-oliveira
Copy link
Collaborator

I'm OK with both.

@paulo-ferraz-oliveira
Copy link
Collaborator

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.

@elbrujohalcon
Copy link
Member Author

I'm not sure if there is an easy way… My plan was to do it The Hard Way™️

@elbrujohalcon
Copy link
Member Author

elbrujohalcon commented Dec 9, 2020

  • Activate github discussions?
  • Turn this thing into the first discussion there?

@paulo-ferraz-oliveira
Copy link
Collaborator

I'm OK with Discussions and making this the first discussion 😄

@paulo-ferraz-oliveira
Copy link
Collaborator

paulo-ferraz-oliveira commented Dec 9, 2020

(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
[5] I'll include this in the same pull request as [2]: 4c56984

@paulo-ferraz-oliveira
Copy link
Collaborator

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.

@elbrujohalcon
Copy link
Member Author

Yeah… My plan is to work on the movement of tickets and stuff at some point during my vacations. That is… in 2 weeks.

@paulo-ferraz-oliveira
Copy link
Collaborator

What else could I do to help here?

@elbrujohalcon
Copy link
Member Author

What else could I do to help here?

Wait... I guess 😜

@elbrujohalcon
Copy link
Member Author

Done.

@paulo-ferraz-oliveira
Copy link
Collaborator

El hombre.

@paulo-ferraz-oliveira paulo-ferraz-oliveira removed their assignment Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants