Bump to version 0.4.1

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -1,61 +0,0 @@
-name: Bug Report
-description: File a bug report
-title: "[Bug]: "
-labels: ["bug"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this bug report!
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected behavior
-      description: How do you expect the
-      value: "Something should happen"
-    validations:
-      required: true
-  - type: textarea
-    id: what-happened
-    attributes:
-      label: Actual behavior
-      description: How is what happened different from the expected behavior?
-      value: "Something else happened"
-    validations:
-      required: true
-  - type: dropdown
-    id: package-version
-    attributes:
-      label: org-unique-id version
-      description: What version of org-unique-id are you using?
-      options:
-        - master
-        - 0.4.1
-        - 0.4.0
-        - 0.3.1
-        - 0.3.0
-        - something else (please specify)
-  - type: dropdown
-    id: emacs-version
-    attributes:
-      label: Emacs version
-      description: Which version of Emacs are you using?
-      options:
-        - 28.1
-        - 27.2
-        - 27.1
-        - 26.3
-        - 26.2
-        - 26.1
-        - 25.3
-        - 25.2
-        - 25.1
-        - master
-        - something else (please specify)
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant code or log output
-      description: Please copy and pase any relevant code or log output. This will be automatically formatted into code, so no need for backticks
-      render: emacs-lisp

.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml

@@ -1,33 +0,0 @@
-name: Feature Request
-description: Request a new feature
-title: "[Feature Request]: "
-labels: ["enhancement"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to request a new feature!
-  - type: textarea
-    id: feature-description
-    attributes:
-      label: New feature
-      description: Description of the new feature
-      value: "New function org-unique-id-thing should do thing"
-    validations:
-      required: true
-  - type: textarea
-    id: feature-reason
-    attributes:
-      label: Why this new feature
-      description: Describe why this new feature should be added to org-unique-id
-      value: "New function org-unique-id-thing does something often done by people"
-    validations:
-      required: true
-  - type: textarea
-    id: ideas-implementation
-    attributes:
-      label: Implementation ideas and additional thoughts
-      description: Do you have an idea on how to implement it?
-      value: "It could be implemented doing foo, bar, and baz"
-    validations:
-      required: false

CONTRIBUTING.org

@@ -32,7 +32,7 @@ information as possible:
 As you are collecting these pieces of information, try to come up with
 a short and clear issue title –it should describe quickly your issue
 without being too vague (e.g. avoid stuff like “error when opening
-org-mode” or “doesn’t work”).
+Eshell” or “doesn’t work”).
 
 ** Submitting New Code
 If you are submitting new code through a pull request, make sure of
@@ -75,10 +75,10 @@ clear as to what it is meant to do. Its description should:
 ** Finding Something To Do
 Not sure where to begin? Take a look at the list of open issues,
 especially the ones with one of the following labels:
-- [[https://github.com/Phundrak/org-unique-id/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22good+first+issue%22][/good first issue/]] :: These issues indicate easy to fix issues and
+- [[https://github.com/Phundrak/eshell-info-banner.el/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22good+first+issue%22][/good first issue/]] :: These issues indicate easy to fix issues and
   easy to implement enhancements. If you are a beginner or if you want
   to familiarize yourself with the package, look for these issues.
-- [[https://github.com/Phundrak/org-unique-id/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+sort%3Aupdated-desc][/help wanted/]] :: These issues might require some more work than /good
+- [[https://github.com/Phundrak/eshell-info-banner.el/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+sort%3Aupdated-desc][/help wanted/]] :: These issues might require some more work than /good
   first issue/ issues and might be a bit more interesting.
 If you want to work on an open issue, leave a comment saying
 so. However, you can directly submit a pull request if you are simply

org-unique-id.el

@@ -34,16 +34,16 @@
 ;;
 ;; In order to be enabled, this package’s `org-unique-id-maybe'
 ;; function must be hooked to `before-save-hook', and the string
-;; \\='unique-id:t\\=' must be present in an \\='#+OPTIONS:\\=' line
-;; in the buffer.
+;; \\='auto-id:t\\=' must be present in an \\='#+OPTIONS:\\=' line in
+;; the buffer.
 ;;
-;; If the \\='unique-id:t\\=' string is found, then it will create a
+;; If the \\='auto-id:t\\=' string is found, then it will create a
 ;; slug of the current header (and if there are, its parent headers)
 ;; and it will add a unique string suffix generated with a UUID
 ;; generator to ensure all IDs are unique.
 ;;
 ;; Here is an example of an org-mode file without the
-;; \\='unique-id:t\\=' option after save:
+;; \\='auto-id:t\\=' option after save:
 ;;
 ;;     #+title: Test file
 ;;     * Test level 1