You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release brings official support for ARM architecture. From now on, our Docker builds are multi-platform. You can now run IntelOwl in your favourite ARM machine smoothly, e.g. Apple Silicon Mac and Raspberry PI.
8
+
9
+
We have few new analyzers that you can play with (in particular new Vulnerability scanners like WAD, Nuclei) and updated Abuse.Ch analyzers to allow the configuration of your API key.
10
+
11
+
Then we have a lot of fixes and dependencies upgrades as usual.
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@ Please delete options that are not relevant.
28
28
-[ ] If the plugin interacts with an external service, I have created an attribute called precisely `url` that contains this information. This is required for Health Checks.
29
29
-[ ] If the plugin requires mocked testing, `_monkeypatch()` was used in its class to apply the necessary decorators.
30
30
-[ ] I have added that raw JSON sample to the `MockUpResponse` of the `_monkeypatch()` method. This serves us to provide a valid sample for testing.
31
+
-[ ] I have inserted the copyright banner at the start of the file: ```# This file is a part of IntelOwl https://github.com/intelowlproject/IntelOwl # See the file 'LICENSE' for copying permission.```
31
32
-[ ] If external libraries/packages with restrictive licenses were used, they were added in the [Legal Notice](https://github.com/certego/IntelOwl/blob/master/.github/legal_notice.md) section.
32
33
-[ ] Linters (`Black`, `Flake`, `Isort`) gave 0 errors. If you have correctly installed [pre-commit](https://intelowlproject.github.io/docs/IntelOwl/contribute/#how-to-start-setup-project-and-development-instance), it does these checks and adjustments on your behalf.
33
34
-[ ] I have added tests for the feature/bug I solved (see `tests` folder). All the tests (new and old ones) gave 0 errors.
@@ -38,4 +39,4 @@ Please delete options that are not relevant.
38
39
39
40
### Important Rules
40
41
- If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
41
-
- Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.
42
+
- Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review by using GitHub's reviewing system detailed [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review).
workflow_dispatch: # Allows the workflow to be triggered manually
7
+
8
+
jobs:
9
+
stale:
10
+
runs-on: ubuntu-latest
11
+
steps:
12
+
- uses: actions/stale@v9
13
+
with:
14
+
repo-token: ${{ github.token }}
15
+
stale-pr-message: "This pull request has been marked as stale because it has had no activity for 10 days. If you are still working on this, please provide some updates or it will be closed in 5 days."
16
+
close-pr-message: "This pull request has been closed because it had no updates in 15 days. If you're still working on this fell free to reopen."
0 commit comments