1
0
Форкнуть 0
Repo containing code for filing issues from the webcompat-blipz-experiement web extension
Перейти к файлу
Mike Taylor 0cf31b2171
Merge pull request #54 from mozilla/dependabot/pip/urllib3-1.24.2
Bump urllib3 from 1.24 to 1.24.2
2019-05-28 12:22:43 -05:00
.circleci Issue #2. Add circleci config file. 2018-05-04 18:50:42 -05:00
app Fixes #49. Accept PNG in addition to JPEG. 2018-11-30 16:58:15 -06:00
tests Issue #49. Update tests. 2018-11-30 16:58:15 -06:00
.env Issue #16. Add a bit more structure to the app. 2018-05-11 18:02:03 -05:00
.gitignore Add functional toy server for filing issues. 2018-05-01 16:49:43 -05:00
CODE_OF_CONDUCT.md Add Mozilla Code of Conduct file 2019-03-29 23:54:02 -07:00
LICENSE Add functional toy server for filing issues. 2018-05-01 16:49:43 -05:00
Pipfile Issue #47. Upgrade requests 2018-10-29 20:55:56 -05:00
Pipfile.lock Bump urllib3 from 1.24 to 1.24.2 2019-05-28 17:21:47 +00:00
Procfile No issue. Update Procfile. 2018-05-15 14:37:56 -05:00
README.md No issue. Fix formatting of code in README 2018-05-16 14:17:33 -05:00
run.py Issue #16. Add a bit more structure to the app. 2018-05-11 18:02:03 -05:00

README.md

webcompat-blipz-experiment-issues

CircleCI

Repo used to host the code for filing issues from the webcompat-blipz-experiement web extension. Actual user-reported issues are not filed here, but elsewhere.

Local installation

We're using pipenv for this project. Be sure to install it first.

  1. clone the repo
  2. pipenv sync --dev
  3. pipenv run flask run

Note: If you're trying to use this in production, it will expect a lot of environment variables. Check out config.py.

🚨 Please don't ever add any to the .env file and check it in. 🚨

How it works

This server exposes a /new endpoint that expects the following multipart/form-data payload via POST, represented here in some kind of pseudo-schema:

{
  "body": the issue body (required)
  "title": the issue title (required),
  "screenshot": base64 encoded jpeg (optional),
  "labels": array of strings (optional)
}

A GitHub issue will be created, assuming all the credentials are correct, and if there's a screenshot in the payload, it will be uploaded to a private s3 bucket. Once that is done, a link to the uploaded image will be posted as a comment in the newly created issue. For privacy and security reasons, the GitHub repo and its issues are private and locked down to a small team of Mozilla employees within the @mozilla GitHub org. If you think you need access, ping miket@mozilla.com. The s3 bucket is restricted to people with IAM access, and the images are not accessible from GitHub issues.