Secure api_key storage in zuliprc with automatic & manual encryption

.editorconfig

@@ -0,0 +1,26 @@
+# See https://editorconfig.org
+
+root = true
+
+[*]
+end_of_line = lf
+charset = utf-8
+indent_size = 4
+indent_style = space
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.{py,pyi}]
+max_line_length = 88
+
+[*.{md,yaml,yml}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab
+
+[*.diff]
+trim_trailing_whitespace = false
+
+[.git/*]
+trim_trailing_whitespace = false

.github/ISSUE_TEMPLATE/01_crash.md

@@ -0,0 +1,39 @@
+---
+name: Bug report (major)
+about: A major bug which significantly impacts usability, eg. an unexpected quit, crash, freeze.
+labels: 'bug: crash,'
+---
+
+### Bug description
+
+
+
+<!-- If discussed in #zulip-terminal or another channel on chat.zulip.org, paste link below: -->
+
+
+### How is the bug triggered?
+How can you reproduce the bug?
+1.
+
+
+### Does it produce a 'traceback' or 'exception'?
+<!-- Copy/paste it between the ``` lines below: -->
+```
+
+
+```
+
+### How are you running the application?
+Please include as many of the following as possible:
+- **Zulip-terminal version:**
+  eg. a specific version (0.7.0), or if running from `main` also ideally the git ref
+- **Zulip server version(s):**
+  eg. Zulip Cloud, the version you are running self-hosted, or the Zulip Community server (chat.zulip.org)
+- **Operating system (and version):**
+  eg. Debian Linux, Ubuntu Linux, macOS, WSL in Windows, Docker
+- **Python version (and implementation):**
+  eg. 3.8, 3.9, 3.10, ... (implementation is likely to be eg. CPython, or PyPy)
+
+If possible, please provide details from the `About` menu: (hotkey: Meta + ?)
+(this can provide some of the details above)
+

.github/ISSUE_TEMPLATE/02_bug.md

@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: A concrete bug report with steps to reproduce the behavior.
+labels: 'bug,'
+---
+
+### Bug description
+
+
+
+<!-- If discussed in #zulip-terminal or another channel on chat.zulip.org, paste link below: -->
+
+
+### How is the bug triggered?
+How can you reproduce the bug?
+1.
+
+
+### What did you expect to happen?
+
+
+
+### How are you running the application?
+Please include as many of the following as possible:
+- **Zulip-terminal version:**
+  eg. a specific version (0.7.0), or if running from `main` also ideally the git ref
+- **Zulip server version(s):**
+  eg. Zulip Cloud, the version you are running self-hosted, or the Zulip Community server (chat.zulip.org)
+- **Operating system (and version):**
+  eg. Debian Linux, Ubuntu Linux, macOS, WSL in Windows, Docker
+- **Python version (and implementation):**
+  eg. 3.8, 3.9, 3.10, ... (implementation is likely to be eg. CPython, or PyPy)
+
+If possible, please provide details from the `About` menu: (hotkey: Meta + ?)
+(this can provide some of the details above)
+

.github/ISSUE_TEMPLATE/03_parity.md

@@ -0,0 +1,25 @@
+---
+name: Feature request (a missing known Zulip feature)
+about: A request for a feature which is missing, but present in another Zulip client (eg. Web/Desktop/mobile).
+labels: 'missing feature,'
+---
+
+### Description of feature missing from another Zulip client
+<!-- Is this an entire missing feature? Or part of the feature? -->
+
+
+
+<!-- If discussed in #zulip-terminal or another channel on chat.zulip.org, paste link below: -->
+
+
+### When was this feature first available in Zulip?
+If you know:
+- **Zulip version:**
+  (eg. 2.1, 5.0, 8.0, ..., or 'Zulip Cloud today')
+- **Zulip feature level:**
+  (see https://zulip.com/api/changelog)
+
+
+### Other details
+
+

.github/ISSUE_TEMPLATE/04_platform.md

@@ -0,0 +1,19 @@
+---
+name: Feature suggestion
+about: A suggestion for an improvement, specific to the capabilities of the terminal environment.
+labels: 'enhancement,'
+---
+
+<!--
+NOTE: If your proposed feature:
+1) is already available in Zulip, please use the other issue feature category
+2) would be of benefit to Zulip clients generally, please instead report it at:
+   https://github.com/zulip/zulip/issues/new/choose
+-->
+
+### Description of suggested feature
+
+
+
+<!-- If discussed in #zulip-terminal or another channel on chat.zulip.org, paste link below: -->
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Report broader Zulip issues (beyond Zulip-Terminal)
+    about: Includes links to best-practices for filing bug reports, feature requests, security vulnerabilities and more.
+    url: https://github.com/zulip/zulip/issues/new/choose
+  - name: Not sure?
+    about: 'Chat with us, using any of the Zulip clients, in #zulip-terminal on the Developer Community server (chat.zulip.org).'
+    url: https://zulip.com/development-community

.github/pull_request_template.md

@@ -1,36 +1,42 @@
-<!-- Please see https://github.com/zulip/zulip-terminal#contributor-guidelines ! -->
-
-**What does this PR do?**  <!-- Overall description goes here -->
-
-<!-- If fixing a filed bug or new feature, add 'Fixes #<issue>' or 'Partial fix for #<issue>' -->
-
-<!-- Add a link to a discussion on chat.zulip.org, if relevant -->
-
-**Tested?** <!-- Fine to leave some of these unchecked if this is a draft/work-in-progress -->
-- [ ] Manually
-- [ ] Existing tests (adapted, if necessary)
-- [ ] New tests added (for any new behavior)
-- [ ] Passed linting & tests (each commit)
-<!-- Code must pass CI (GitHub Actions) before merging - look for the green tick! -->
-
-<!-- See https://github.com/zulip/zulip-terminal#commit-style -->
-**Commit flow** <!-- if more than one commit; add/delete/fill-in as appropriate -->
-<!-- For example:
-- first commit doing some thing
-- maybe multiple commits doing similar things
+<!-- See README for documentation, or ask in #zulip-terminal if unclear -->
+### What does this PR do, and why?
+
+
+
+### Outstanding aspect(s)    <!-- DELETE SECTION IF EMPTY -->
+<!-- In what ways is this not fully implemented/functioning? Compared to a discussion/issue? -->
+<!-- Do you not understand something? Are you unsure about a certain approach? Want feedback? -->
+- [ ] 
+
+### External discussion & connections
+<!-- [x] all that apply, specifying topic and adding numbers after # for issues/PRs -->
+- [ ] Discussed in **#zulip-terminal** in `topic`
+- [ ] Fully fixes #
+- [ ] Partially fixes issue #
+- [ ] Builds upon previous unmerged work in PR #
+- [ ] Is a follow-up to work in PR #
+- [ ] Requires merge of PR #
+- [ ] Merge will enable work on #
+
+### How did you test this?
+<!-- [x] all that apply -->
+- [ ] Manually - Behavioral changes
+- [ ] Manually - Visual changes
+- [ ] Adapting existing automated tests
+- [ ] Adding automated tests for new behavior (or missing tests)
+- [ ] Existing automated tests should already cover this (*only a refactor of tested code*)
+
+### Self-review checklist for each commit
+- [ ] It is a [minimal coherent idea](https://github.com/zulip/zulip-terminal#structuring-commits---speeding-up-reviews-merging--development)
+- [ ] It has a commit summary following the [documented style](https://github.com/zulip/zulip-terminal#structuring-commits---speeding-up-reviews-merging--development) (title & body)
+- [ ] It has a commit summary describing the  motivation and reasoning for the change
+- [ ] It individually passes linting and tests
+- [ ] It contains test additions for any new behavior
+- [ ] It flows clearly from a previous branch commit, and/or prepares for the next commit
+
+### Visual changes    <!-- DELETE SECTION IF NO VISUAL CHANGE -->
+<!-- Zulip tips at https://zulip.readthedocs.io/en/latest/tutorials/screenshot-and-gif-software.html -->
+<!-- For video, try asciinema; after uploading, embed using
+[![yourtitle](https://asciinema.org/a/<id>.png)](https://asciinema.org/a/<id>)
 -->
-
-**Notes & Questions** <!-- if any; add/delete/fill-in as appropriate -->
-<!-- For example:
-- this doesn't include feature X (yet?)
-- unsure about Y
-- should this do Z?
--->
-
-**Interactions** <!-- if any; add/delete/fill-in as appropriate -->
-<!-- eg.
-- Waiting on #<PR>
-- Blocks #<PR>
--->
-
-**Visual changes** <!-- if any; add/delete/fill-in with screenshot/diagram as appropriate -->
+<!-- NOTE: Attached videos/images will be clearer from smaller terminal windows -->

.github/workflows/codeql-analysis.yml

@@ -14,39 +14,43 @@ concurrency:
   group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
   cancel-in-progress: true
 
+permissions:
+  contents: read
+
 jobs:
   analyse:
     name: Analyse
+    if: ${{!github.event.repository.private}}
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
     runs-on: ubuntu-latest
 
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v3
+      uses: actions/checkout@v4
       with:
         persist-credentials: false
     - name: Set up Python
-      uses: actions/setup-python@v4
+      uses: actions/setup-python@v5
       with:
         python-version: '3.9'
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
         pip3 install .
-
-        # Set the `CODEQL-PYTHON` environment variable to the Python executable
-        # that includes the dependencies
-        echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@v2
+      uses: github/codeql-action/init@v3
       with:
         languages: python
         # Override the default behavior so that the action doesn't attempt
         # to auto-install Python dependencies
         setup-python-dependencies: false
-      
+
       # Override language selection by uncommenting this and choosing your languages
       # with:
       #   languages: go, javascript, csharp, python, cpp, java
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v2
+      uses: github/codeql-action/analyze@v3