microsoft / microsoft/BotFramework-WebChat
Create GitHub actions/bot
Open
Nobody has claimed this yet.
backlog
front-burner
team-agility
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Old issue name: "Concise list of ways to increase team agility"
New name: "Create GitHub actions/bot"
(Other work items have been scoped out to other issues)
- GitHub actions/bot
- Close and lock Duplicates
- Lock issues that are released (has merged PR) & stale
- Squash merging PRs for out-of-date branches
- Auto merge passing & approved PRs (e.g. docs change)
- GitHub Project Automation
- Link checker (report broken urls)
Old content
- Corina to compile notes and existing issues here; take a look at
team-agilitylabel - High priority to tooling that will help team members onramp for debugging & setting up projects more efficiently
- Make available to compulim for additions/edits
- Present to Web Chat team.
- @compulim Are we able to create a private repo? Are there rules about being public?
- answer: No
P0- https://github.com/microsoft/BotFramework-WebChat/issues/3535: Detailed TSG of how to investigate Web Chat problems before escalation.P0- https://github.com/microsoft/BotFramework-WebChat/issues/3522: Private internal repo (e.g. BotFramework-WebChat-Support) for projects with long setup times- SharePoint / SPFX -- will need hosting
- Dynamics 365 -- will need hosting
- Cordova
- Angular
- Xamarin
- (All speech enabled)
- TSGs for all inside botframework-webchat repo
P1- https://github.com/microsoft/BotFramework-WebChat/issues/2575: Add more Adaptive Cards to Mock Bot with recent AC updates- Add tests
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
No source files or tests are named. Start by reviewing the listed GitHub Actions and bot candidates, including duplicate handling, stale issue locking, PR merging, project automation, and link checking. Done requires narrowing the list into a scoped implementation and completing the selected automation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100