General Project Update

- Closes #1263.
-  Added Workflows for issue-management.

.github/workflows/main.yml

@@ -0,0 +1,36 @@
+name: Close invalid and inactive issues
+on:
+  issues:
+    types: [opened, edited]
+  schedule:
+    - cron: "00 1 * * *"
+
+jobs:
+  auto_close_issues:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v1
+      - name: Automatically close issues that don't follow the issue template
+        uses: lucasbento/auto-close-issues@v1.0.2
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          issue-close-message: "@${issue.user.login}: This issue is being automatically closed because it does not follow the issue template." # optional property
+          closed-issues-label: "declined" # optional property
+
+  close-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/stale@v4
+        with:
+          days-before-issue-stale: 120
+          days-before-issue-close: 14
+          stale-issue-label: "stale"
+          stale-issue-message: "This issue is stale because it has been open for 120 days with no activity."
+          close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
+          days-before-pr-stale: 1
+          days-before-pr-close: 1
+          repo-token: ${{ secrets.GITHUB_TOKEN }}

doc/compiling.md

@@ -119,14 +119,18 @@ or execute (Debian-based systems only): `apt-get install gcc build-essential cma
 
 1. Change into the project source directory: `cd stlink`
 2. Run `make clean` -- required by some linux variants.
-3. Run `make release` to create the _Release_ target
+3. Run `make release` to create the _Release_ target.
 4. Run `make install` to full install the package with complete system integration. This might require sudo permissions.
 5. Run `make debug` to create the _Debug_ target (_optional_)<br />
    The debug target is only necessary in order to modify the sources and to run under a debugger.
 6. Run `make package`to build a Debian Package. The generated packages can be found in the subdirectory `./build/dist`.
 
 As an option you may also install to an individual user-defined folder e.g `$HOME` with `make install DESTDIR=$HOME`.
 
+### How to avoid the error message: "Can not open shared object file"
+
+When installing system-wide (`sudo make install`) the dynamic library cache needs to be updated with the command `ldconfig`.
+
 #### Removal:
 
 1. Run `make uninstall` to perform a clean uninstall of the package from the system.
@@ -216,7 +220,7 @@ To do this with only one simple command, type:
 2. Run `make clean` to clean remnants of any previous builds.
 3. Run `make release` to create the _Release_ target
 4. Run `make install` to full install the package with complete system integration. This might require sudo permissions.
-5. Run `make debug` to create the _Debug_ target (_optional_)<br />
+5. Run `make debug` to create the _Debug_ target. (_optional_)<br />
    The debug target is only necessary in order to modify the sources and to run under a debugger.
 
 As an option you may also install to an individual user-defined folder e.g `$HOME` with `make install DESTDIR=$HOME`.