Skip to content

Commit

Permalink
Merge pull request #22 from Joel-hanson/typo-fix
Browse files Browse the repository at this point in the history
The typo in configuration key fixed issue #12
  • Loading branch information
Joel-hanson authored Sep 6, 2020
2 parents ee95de6 + 73f950e commit 891a597
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ In addition to the deployment options you must also configure the following.

| Key | Value Information | Type | Required | Default |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | -------- | -------- |
| `FLASK8` | This boolean flag to whether to run flake8 linting for our project. | `with` | **No** | false |
| `FLAKE8` | This boolean flag to whether to run flake8 linting for our project. | `with` | **No** | false |
| `PYTHON_VERSION` | Version range or exact version of a Python version to use, using SemVer's version range syntax. | `with` | **Yes** | 3.6.10 |
| `FLAKE8_CONFIG_FILE` | The flake8 config path relative to the github repository (this requires input flake8 to be true). | `with` | **No** | ".flake8" |
| `DEPLOY` | Deploy to AWS Elastic beanstalk. | `with` | **Yes** | true |
Expand Down
2 changes: 1 addition & 1 deletion action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ description: "Github action for deploying the Django project to Elastic beanstal
author: "[email protected]"

inputs:
flask8:
flake8:
description: "Do we need to run flake8 linting?"
required: true
default: true
Expand Down

0 comments on commit 891a597

Please sign in to comment.