Add GitHub Actions workflow for scheduled team sync

[Copilot]

Enables running team sync as a scheduled GitHub Actions workflow, eliminating the need for a persistent webhook server.

Changes

New workflow: .github/workflows/sync-teams.yml

• Runs hourly via cron (configurable)
• Manual trigger with test mode option
• Supports all backends: Google Workspace, LDAP, Azure AD, Okta, OneLogin, Keycloak
• Configuration via GitHub Secrets
• Minimal permissions (contents: read)
• Cleanup of sensitive files (private keys, credentials, syncmap)

Documentation restructured with Google Workspace focus:

• README.md: Streamlined to focus on GitHub Actions with Google Workspace (reduced from 345 to 157 lines)
  • Quick start guide for Google Workspace integration
  • Clear prerequisites and configuration steps
  • Troubleshooting section
  • Links to detailed documentation
• docs/ folder: Organized detailed documentation to minimize markdown sprawl
  • docs/google-workspace.md - Detailed Google Workspace configuration
  • docs/other-backends.md - LDAP, Azure AD, Okta, OneLogin, Keycloak
  • docs/github-app-setup.md - GitHub App creation and permissions
  • docs/additional-settings.md - Advanced configuration options
  • docs/alternative-deployment.md - Webhook server and script modes

Usage

Configure secrets in repository settings, enable the workflow. The app already supports running as a one-time script when FLASK_APP is unset:

if __name__ == "__main__":
    if "FLASK_APP" in os.environ:
        app.run(...)
    else:
        sync_all_teams()  # ← Used by Actions workflow

Schedule configurable via cron expression in workflow file.

• Fixes Run from Github Actions #1

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Run from Github Actions</issue_title>
<issue_description>Enable github actions workflow for syncing users/groups from Google Workplace.

Document this as appropriate in standard files and directories with minimal .md sprawl.

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Run from Github Actions #1

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[cpritchett]

@copilot re-orient readme around current workflow (and focus on google workspace integration). Move all other setup info to docs/ folder.

[Copilot]

@copilot re-orient readme around current workflow (and focus on google workspace integration). Move all other setup info to docs/ folder.

Done in commit c034025.

Changes:

• README now focuses on GitHub Actions with Google Workspace (157 lines, down from 345)
• Created docs/ folder with detailed guides for all backends and deployment options
• Moved all detailed setup info to organized documentation files:
  • docs/google-workspace.md - Google Workspace configuration
  • docs/other-backends.md - LDAP, Azure AD, Okta, OneLogin, Keycloak
  • docs/github-app-setup.md - GitHub App setup
  • docs/additional-settings.md - Advanced configuration
  • docs/alternative-deployment.md - Webhook server and script modes

The README now provides a quick start focused on the GitHub Actions workflow with Google Workspace, with links to detailed documentation in the docs/ folder.