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

tgve/eAtlas branch revamp/restructure #96

Closed
layik opened this issue Jan 7, 2022 · 2 comments
Closed

tgve/eAtlas branch revamp/restructure #96

layik opened this issue Jan 7, 2022 · 2 comments

Comments

@layik
Copy link
Collaborator

layik commented Jan 7, 2022

For clarification, the branch was the main dev repo for eAtlas/TGVE and has now grown out of its purpose.

  • master branch is now way behind branch npm
  • branch npm is the most important part, npm-dev is where I do work and create PRs on npm.
  • Wiki is the main docs for "the project"
  • Dockerfile is based on "old" approach of building the front-end using JS tools (npm)

Must be done:

  • README to serve as pointer to Wiki/docs and other repo docs etc
  • master branch => npm branch?
  • etc

Consider doing:

  • ??
@rolyp rolyp transferred this issue from another repository Jan 14, 2022
@rolyp
Copy link
Contributor

rolyp commented Jan 14, 2022

@layik Moved this from the reg repo and will consolidate into #64.

@rolyp rolyp mentioned this issue Jan 14, 2022
10 tasks
@rolyp
Copy link
Contributor

rolyp commented Jan 14, 2022

Merged into #64

@rolyp rolyp closed this as completed Jan 14, 2022
@rolyp rolyp changed the title tgve/eAtlas branch revamp/restructure - discuss tgve/eAtlas branch revamp/restructure Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants