Assembly Telegram Bots is a focused engineering organization building automated solutions for the Telegram platform. Our work spans serverless bot infrastructure, AI-powered code analysis pipelines, and GitHub Actions workflows — all designed around practical utility and minimal operational overhead.
The organization maintains two primary product lines: production-ready Telegram bots built on both Python and Google Apps Script runtimes, and a suite of LLM-integrated GitHub Actions for automated code review and issue generation.
The codebase is organized around two distinct runtime paradigms:
actions_* repositories — Python-based bots deployed and triggered via GitHub Actions. Suited for scheduled tasks, event-driven automation, and workloads requiring full Python library access.
GAP_* repositories — Google Apps Script bots. Truly serverless, zero-infrastructure deployments ideal for lightweight automation, scheduled broadcasts, and Google Workspace integration.
Automated GitHub Actions that use large language models to perform code review, security auditing, and issue generation directly from commits and pull requests. Each variant targets a different LLM provider, allowing teams to integrate with their existing AI infrastructure.
| Repository | Model | License |
|---|---|---|
| Issues-github-actions-GPT-4o | OpenAI GPT-4o | AGPL-3.0 |
| Issues-github-actions-gemeniAI | Google Gemini | AGPL-3.0 |
| Issues-github-actions-Llama | Meta Llama | AGPL-3.0 |
All three share the same interface: on push or pull request, the action analyzes the diff, generates a structured review, and opens a GitHub Issue with findings — security flags, code quality notes, and improvement suggestions included.
git clone https://github.com/Assembly-telegram-bots/<repo>.git
cd <repo>
pip install -r requirements.txt
cp .env.example .env
# Set TELEGRAM_BOT_TOKEN and any required API keys
python bot.pyCopy the source into a new project at script.google.com, configure your ScriptProperties with the required tokens, and set up a time-based trigger for scheduled execution. No server required.
Add the workflow file to .github/workflows/ in your repository and configure the following secrets in your repository settings:
OPENAI_API_KEY # for GPT-4o variant
GEMINI_API_KEY # for Gemini variant
LLAMA_API_KEY # for Llama variant
GITHUB_TOKEN # standard Actions token
Pull requests are welcome. For significant changes, open an issue first to discuss the proposed direction.
1. Fork the repository
2. Create a feature branch — git checkout -b feature/your-feature
3. Commit your changes — git commit -m 'feat: description'
4. Push the branch — git push origin feature/your-feature
5. Open a Pull Request
Please follow the existing code style and include relevant documentation updates with your changes.
