Skip to content

Commit

Permalink
Fix warnings by lint
Browse files Browse the repository at this point in the history
  • Loading branch information
fisuda committed Oct 8, 2023
1 parent 8379935 commit ac0b6e7
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 30 deletions.
20 changes: 10 additions & 10 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@ assignees: ''
**Checklist**
_Put an `x` in the boxes that apply_

- [ ] I have run the latest release.
- [ ] I have inspeced the status of docker containers.
- [ ] I have run the sanity check described in after-installation.md.
- [ ] I have inspected all error messages.
- [ ] I have inspected the log files in the /var/log/fiware directory.
- [ ] I have run the `make collect` command.
- [ ] I have provided a Github Star to this repository.
- \[ \] I have run the latest release.
- \[ \] I have inspeced the status of docker containers.
- \[ \] I have run the sanity check described in after-installation.md.
- \[ \] I have inspected all error messages.
- \[ \] I have inspected the log files in the /var/log/fiware directory.
- \[ \] I have run the `make collect` command.
- \[ \] I have provided a Github Star to this repository.

**Describe the bug**
A clear and concise description of what the bug is.
Expand All @@ -35,9 +35,9 @@ A clear and concise description of what you expected to happen.
If applicable, add screenshots to help explain your problem.

**Server (please complete the following information):**
- OS and OS version:
- Docker version:
- Docker Compose version:
- OS and OS version:
- Docker version:
- Docker Compose version:

**Additional context**
Add any other context about the problem here.
Expand Down
16 changes: 8 additions & 8 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,21 +18,21 @@ A clear and concise description of what you want to happen.

**Describe why you need this feature**

- [ ] To approach a new use case.
- [ ] To integrate a new Generic Enabler / othe open source component.
- [ ] To improve or simplify an scenario.
- [ ] Other reason (describe it)
- \[ \] To approach a new use case.
- \[ \] To integrate a new Generic Enabler / othe open source component.
- \[ \] To improve or simplify an scenario.
- \[ \] Other reason (describe it)

**Additional information**

Add any other information, diagrams or screenshots about the feature request here.

**Do you have the intention to implement the solution**

- [ ] Yes, I have the knowledge to implement this new feature.
- [ ] Yes, but I will need help.
- [ ] No, I do not have the skills.
- \[ \] Yes, I have the knowledge to implement this new feature.
- \[ \] Yes, but I will need help.
- \[ \] No, I do not have the skills.

**Other information**

- [ ] I have provided a Github Star to this repository.
- \[ \] I have provided a Github Star to this repository.
24 changes: 12 additions & 12 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,25 +8,25 @@ the `v0.36.0-next` branch.

What types of changes does your code introduce to the project: _Put an `x` in the boxes that apply_

- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Update docker image version of FIWARE GE.
- [ ] Update only documentation, not any source code.
- \[ \] Bugfix (non-breaking change which fixes an issue)
- \[ \] New feature (non-breaking change which adds functionality)
- \[ \] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- \[ \] Update docker image version of FIWARE GE.
- \[ \] Update only documentation, not any source code.

## Checklist

_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code._

- [ ] I have read the [CONTRIBUTING](https://github.com/lets-fiware/FIWARE-Big-Bang/blob/main/CONTRIBUTING.md) doc
- [ ] I have signed the [CLA](https://github.com/lets-fiware/FIWARE-Big-Bang/blob/main/FIWARE-Big-Bang-individual-cla.pdf)
- [ ] I have updated the change log (CHANGELOG.md)
- [ ] I send this pull request to the `v0.36.0-next` branch.
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] I have added necessary documentation (if appropriate)
- [ ] Any dependent changes have been merged and published in downstream modules
- \[ \] I have read the [CONTRIBUTING](https://github.com/lets-fiware/FIWARE-Big-Bang/blob/main/CONTRIBUTING.md) doc
- \[ \] I have signed the [CLA](https://github.com/lets-fiware/FIWARE-Big-Bang/blob/main/FIWARE-Big-Bang-individual-cla.pdf)
- \[ \] I have updated the change log (CHANGELOG.md)
- \[ \] I send this pull request to the `v0.36.0-next` branch.
- \[ \] I have added tests that prove my fix is effective or that my feature works
- \[ \] I have added necessary documentation (if appropriate)
- \[ \] Any dependent changes have been merged and published in downstream modules

## Further comments

Expand Down

0 comments on commit ac0b6e7

Please sign in to comment.