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

Add Contributing, Code of Conduct, and Issue/Pull Request templates #36

Open
yodigi7 opened this issue Feb 25, 2019 · 1 comment
Open
Assignees

Comments

@yodigi7
Copy link
Owner

yodigi7 commented Feb 25, 2019

No description provided.

@yodigi7 yodigi7 self-assigned this Feb 25, 2019
@sulha199
Copy link

sulha199 commented Jul 1, 2019

Hi @yodigi7,

What do you think about this angular guideline https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines.

Therefore, after looking at your repository which contains 3 projects. Do you have any reasons why put all of it in one repository instead of breaking it up based on the project? I think it is better to put these in their own repository, so you can have a different contributing rule for the backend which is Java, and for the frontend which is in angular.

Meanwhile, If you need to use each project as a dependency then you can include them as an npm package. Thanks.

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

2 participants