This commit introduces GitHub Actions to build the docs and deploy them
to GitHub Pages with the following behavior:
* The job will only be triggered for pushes to the branches 'develop' or
those starting with 'v' and changes to the 'docs'-folder in order to
avoid excessive triggering.
* Jobs that are triggered concurrently on different branches are
canceled and only the last job will be executed.
The template for this action is taken from the original docusaurus
documentation (https://docusaurus.io/docs/deployment#deploying-to-github-pages).
Closes#16665
> In an ideal world with infinite resources, there would be no need for
> this app.
>
> But in any successful software project, there's always more work to do
> than people to do it. As more and more work piles up, it becomes
> paralyzing. Just making decisions about what work should and shouldn't
> get done can exhaust all available resources. In the experience of the
> maintainers of this app—and the hundreds of other projects and
> organizations that use it—focusing on issues that are actively affecting
> humans is an effective method for prioritizing work.
>
> To some, a robot trying to close stale issues may seem inhospitable or
> offensive to contributors. But the alternative is to disrespect them by
> setting false expectations and implicitly ignoring their work. This app
> makes it explicit: if work is not progressing, then it's stale. A
> comment is all it takes to keep the conversation alive.
https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea
This file add the configuration needed for stale issues and pull requests
to be automatically closed. Defined as follows:
- issues and pull requests with no activity for 270 days will be marked as "status: stale";
- after that, there will be a period of 90 days for the issue or pull request to be claimed, otherwise will be closed.
The bot will never interact/close with issues and pull requests marked as:
- status: vetify
- status: accepted
- target: security
- type: discussion
For this setup to be effective, add https://probot.github.io/apps/stale/
to BigBlueButton repository.
This patch adds a simple GitHub Actions workflow which will
automatically check open pull requests on code changes, adding a comment
and a label if the pull request has conflicts. The label will
automatically be removed again once the conflict has been resolved.
We use this for a while now with opencast and it really helps since
people do not have to manually check if their pull requests need an
update any longer.
An example, of hoe this looks in action can be found at
https://github.com/opencast/opencast/pull/2053#issuecomment-734987582
- Added config.yml for support sources outside of Github based on list from bigbluebutton.org
- Added comment to each issue template about this issue tracker not being for general support questions
- Deleted the general-issue.md template to try to steer support requests to the google groups/forums
