[Checklist] Git Repos Improvements - Githubissues

IDEMSInternational / open-app-builder

PLH App Frontend

GNU General Public License v3.0

5 stars 24 forks source link

[Checklist] Git Repos Improvements #1958

Open chrismclarke opened 1 year ago

chrismclarke commented 1 year ago

Update 2024-03 - Rough outstanding list CI

[ ] Add scripts and templates to make it easier to automatically populate deployment repo actions
[ ] Add actions to automatically open PRs

Repo

[ ] Remove historic large file history and lfs files
[ ] Handle line endings (gitattributes?)
[ ] Ensure git-lfs installed

Scripts

[ ] Rename tasks to providers
[ ] Publish external app scripts package and include in repo with package.json to allow triggering from content repo
[ ] Migrate additional code to ts-morph (e.g. template file)

Git

[ ] Scripts to populate a specific content version/track stable/preview etc. pipelines or branches
[ ] Add support for target app version from content repo and include in build

Potential areas for future development identified in #1755

Core Functionality

[x] Fix CI integrations

Code Tidying

[x] Add outputs for deployment create/import and use for set

CI

[x] Add example actions for standalone deployment (web preview, android release)

Content

[x] PR to remove app-data (once fully deprecated), should also change default app_data.output_path
[x] Populate PLH content repo
[x] Remove hardcode app_data paths from config

Scripts

[x] Possibly refactor script as a provider (e.g. custom provider)
[x] Move all workflows to scripts (?)… unlikely to include custom

Misc

[x] Update release system for core app
[x] Consider an extension system to manage additional deployment settings, e.g. android folder containing splash/icon for generating android assets or capacitor settings (populated on deployment change)
[x] Better feedback on long operations, such as git repo sync for large repo

chrismclarke commented 5 months ago

It's been a while since writing this list, I'd say around half the items have been implemented, a handful likely no longer required and then ideally the rest should be converted to standalone issues.