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

🏗️ Refactor: move PBI reports in dedicated repo #705

Closed
ken-mellem opened this issue Nov 20, 2023 · 4 comments · Fixed by #738
Closed

🏗️ Refactor: move PBI reports in dedicated repo #705

ken-mellem opened this issue Nov 20, 2023 · 4 comments · Fixed by #738
Assignees

Comments

@ken-mellem
Copy link
Contributor

ken-mellem commented Nov 20, 2023

Expected outcome

Cleaner and better repository with better automation and actions.
Making the existing repo faster.
In time saving us from making one huge monorepo.

Status

There is now an action that automates the whole process of creating a report
Im working on moving the reports

@ken-mellem ken-mellem changed the title Refactor: move PBI reports in dedicated repo 🏗️ Refactor: move PBI reports in dedicated repo Nov 20, 2023
@ken-mellem
Copy link
Contributor Author

@aman-riaz fyi - @Gustav-Eikaas is planning on moving all reports in a dedicated repository.
@Gustav-Eikaas update the Description.

@Gustav-Eikaas
Copy link
Contributor

Gustav-Eikaas commented Nov 20, 2023

Let's try to structure them first by category then by specific contexts if applicable

Proposed structure

  • src
    • reports
      -ConstructionAndCommissioning
      -JCA
      -installation
      -Workorder analytics
      -ADS
      -ProjectControl
      -SomethingAnalytics

@Gustav-Eikaas
Copy link
Contributor

@Gustav-Eikaas
Copy link
Contributor

Still working on pipelines in this new repo

@Gustav-Eikaas Gustav-Eikaas linked a pull request Nov 30, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants