Resolve merge conflicts with upstream/main (README, cli.py)

Author: Tahoora-Tabassum

.github/ISSUE_TEMPLATE/bug_issue_template.md

@@ -0,0 +1,29 @@
+---
+name: 'Bug Report Template'
+about: Report a bug to help us improve
+title: 'bug: <context of the bug>'
+labels: bug
+assignees: ''
+
+---
+
+# Bug Report
+
+**Describe the bug**  
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+What you expected to happen.
+
+**Screenshots (optional)**
+Add screenshots if helpful.
+
+**Additional context (optional)**
+Anything else relevant.

.github/ISSUE_TEMPLATE/feature_issue_template.md

@@ -0,0 +1,22 @@
+---
+name: 'Feature Request'
+about: Suggest an idea or enhancement
+title: 'feature: <feature request>'
+labels: enhancement
+assignees: ''
+
+---
+
+# Feature Request
+
+**Describe the feature you'd like**  
+A short description of the desired feature.
+
+**Why is this feature important?**  
+Explain the benefit or use case. Is your feature request related to a problem?
+
+**Describe alternatives you've considered**  
+List any alternative solutions or workarounds considered.
+
+**Additional context**  
+Add any other details or mockups here.

.github/pull_request_template.md

@@ -0,0 +1,25 @@
+# Pull Request
+
+## Description
+
+Briefly describe the changes introduced in this PR.
+
+**Related Issues**
+Link any related issues (e.g., `Issue #12`).
+
+## Type of change
+- [ ] Bug fix (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 change)
+- [ ] This change requires a documentation update
+- [ ] Housekeeping
+
+## Checklist:
+- [ ] My code follows the [ruff code style](http://stellarium.org/doc/head/codingStyle.html) of this project.
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation (if applicable)
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+    - [ ] `poetry run pytest` - all tests passed
+    - [ ] `poetry run ruff check` - no linting errors

.github/workflows/python-CI.yml

@@ -18,24 +18,17 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v3
-    - name: Set up Python 3.10
-      uses: actions/setup-python@v3
+    - uses: actions/checkout@v4
+    - name: Set up Python 3.11
+      uses: actions/setup-python@v5
       with:
-        python-version: "3.10"
+        python-version: "3.11"
     - uses: Gr1N/setup-poetry@v8 #install poetry
-    - name: Install parts of toolchain 
-      run: |
-        python -m pip install --upgrade pip
-        pip install flake8 pytest
+    - name: Upgrade pip
+      run: python -m pip install --upgrade pip
     - name: Install requirements with poetry
       run: poetry install
-    - name: Lint with flake8
-      run: |
-        # stop the build if there are Python syntax errors or undefined names
-        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
-        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
-        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+    - name: Lint with Ruff
+      run: poetry run ruff check --output-format=github .
     - name: Test with pytest
-      run: |
-        poetry run pytest
+      run: poetry run pytest

.gitignore

@@ -1,5 +1,6 @@
 # project-specific
 tmp/
+vault-token.dat
 
 # Byte-compiled / optimized / DLL files
 __pycache__/

Dockerfile

@@ -1,4 +1,4 @@
-FROM python:3.10-slim
+FROM python:3.11-slim
 
 WORKDIR /data