[apps-portfolio] Sync Apps Portfolio to GitHub repo my-sessions-and-bio

[palladius]

This issue is to track the work required to synchronize the Apps Portfolio out to the my-sessions-and-bio GitHub repository.

This will likely involve:

• Reading the data from the Apps Portfolio database.
• Transforming the data into the format required by the my-sessions-and-bio repository (e.g., markdown files).
• Committing and pushing the changes to the my-sessions-and-bio repository.
• Setting up a recurring job or a webhook to trigger the sync.

-- Gemini CLI. as instructed by ricc in .gemini/commands/github/issue.toml

[palladius]

Note: repo is here: https://github.com/palladius/my-sessions-and-bio
Study it a bit and make a plan

[palladius]

Implementation Proposal: /apps-portfolio/sync-out Custom Command

To address the synchronization of data from the local Apps Portfolio to the remote my-sessions-and-bio GitHub repository, I propose implementing a custom command, /apps-portfolio/sync-out.

This command would:

1. Extract Data (from Local): Query the Apps Portfolio database to retrieve relevant talk and event data.
2. Transform Data: Convert the extracted data into the markdown format expected by the my-sessions-and-bio repository. This will involve mapping fields and structuring the output files appropriately.
3. Git Operations (on Remote):
   • Clone the my-sessions-and-bio repository (if not already present).
   • Stage the transformed markdown files within the cloned my-sessions-and-bio repository.
   • Commit the changes with a descriptive message (e.g., "Sync: Updated talks and events from Apps Portfolio").
   • Push the changes to the my-sessions-and-bio repository.
4. Error Handling & Logging: Implement robust error handling for database operations, file transformations, and Git commands. Log all actions and any failures for debugging.

This command could be triggered manually initially, and later integrated into a CI/CD pipeline or a scheduled job for automated synchronization.

-- Gemini CLI. as instructed by ricc in .gemini/commands/github/issue.toml

[palladius]

SGTM. I propose a solution in two phases.

Phase 1

I think we should FIRST start with a try-and-iterate through LLM via a no-code solution, just LLM winging it as we can't foresee the future and pitfalls. The current DB has diverged from remote dB (README) quite a bit. So let's start creationg a Gemini CLI command as above with a smart prompt which roughly gows through the above plan. The final output should be a PR to the other (remote) repo.

Phase 2

Once we've learnt how to do this 1-2 times, we can then refine that command to be more deterministic. For instance, we might have a number of allowlisted commands to execute, like "git clone blah, edit README.md with events, edit some other doc with workshops or CfPs, and so on". Trust user guidance in phase 1 to come up with a perfect phase 2 prompt.

Maybe phase 2 could be some sort of jq / grep in local etc, being fed to an LLM wih the perfect context, like:

Ensure date, location, name , talk name is present in $REPO/$FILE for the following:

* YYYYMMDD (City, State) Talk Name (Riccardo Carlesso)
* {{event 2}}
* {{event 3}}
* ...

[palladius]

For phase 1, please read:

1. https://aipositive.substack.com/p/how-i-turned-gemini-cli-into-a-multi
2. https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/commands.md Custom commands are defined HERE!