actions / actions/starter-workflows
так треба
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
name: Daily KeyCRM Report
on:
schedule:
- cron: '0 9 * * *' # щодня о 9:00 UTC
workflow_dispatch: # можна запускати вручну
jobs:
report:
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v3
- name: Run Python script
uses: actions/setup-python@v4
with:
python-version: '3.x'
- name: Install requests
run: pip install requests
- name: Run report
run: python keycrm_report.py
env:
KEYCRM_API_KEY: ${{ M2IwMjMyOGFmZjE5ZjcwNDA1NDAxMjI2Mzg5ZDM2OGZjYmZjMzZhZQ }}
BOT_TOKEN: ${{ 8302121973:AAGdaEzXyUj2lCHKFMyf1YMXLXFFqczwkPs }}
CHAT_ID: 648619235
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue includes a GitHub Actions workflow that runs keycrm_report.py and installs requests, but names no repository workflow file, expected change, or success condition. Start by inspecting the repository's workflow files and contribution guidance, then clarify what should change before implementation. Completion cannot be determined from the current issue text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100