mutils 1.3.3 โ†’ 1.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: ae172f1ebb8b843113e83445659f54550f47d3340301bef486b2cd3545a3ab17
4
- data.tar.gz: 91e8ec2edfbc8d92619f32c8dc821a0c6d788c7464cb34614dd1fc97211ddbb0
3
+ metadata.gz: a9917adc99336685eaea12d4a2a8dbef1ddf9501c3b9d85fc879788b6fa2a8f6
4
+ data.tar.gz: 86fc9c58f90909cf2dcc622113ea255b0d9c60ca866f0fa113b2004b9cc5df50
5
5
  SHA512:
6
- metadata.gz: 52ddee2122c1297d9edb850710ba8bf5b6aca3e2791055e5f24e7c401895a0198d4f8f418898c8222f6efccb5a15b5bcb1bd832901217988faf1de8b7af519b8
7
- data.tar.gz: 9d42d5c0ceff05296e42be5e902084ea981081c44eb9f8ba4b9bf72fce0654f1c17b9f009fc5fb76c1198b003b0c70291f71be7522503acd215196b0e34d44b9
6
+ metadata.gz: f36f7fa78caa1dbffa90bf34c212b879e54c451cd15574b6f63076c426fb7b2c441f94bd4df92225b8432e3265aac18a851695a652940abb0be7730393b11da7
7
+ data.tar.gz: 00e9ccdf9766bac54e9cf47da6abc4fba179ce40a174d7c08f687be2d1a00f1d73568f537614a362a13168c8443eedd165d1ab8d008850062cc59c1de8da023e
@@ -1,41 +1,46 @@
1
1
  ---
2
- name: Bug report
2
+ name: Bug Report
3
3
  about: Create a report to help us improve
4
- title: ''
5
- labels: ''
6
- assignees: ''
7
-
4
+ title: "[BUG] Briefly describe the issue"
5
+ labels: bug
6
+ assignees: ""
8
7
  ---
9
8
 
10
- Issue tracker is **ONLY** used for reporting bugs. New features should be discussed on our slack channel. Please use [stackoverflow](https://stackoverflow.com) for supporting issues.
9
+ ## Bug Report
10
+
11
+ ### Description:
12
+
13
+ [Provide a clear and concise description of the bug.]
14
+
15
+ ### Steps to Reproduce:
16
+
17
+ 1. [First step]
18
+ 2. [Second step]
19
+ 3. [Third step]
20
+ - [If applicable]
21
+
22
+ ### Expected Behavior:
23
+
24
+ [Describe what you expected to happen.]
11
25
 
12
- <!--- Provide a general summary of the issue in the Title above -->
26
+ ### Actual Behavior:
13
27
 
14
- ## Expected Behavior
15
- <!--- Tell us what should happen -->
28
+ [Describe what actually happened.]
16
29
 
17
- ## Current Behavior
18
- <!--- Tell us what happens instead of the expected behavior -->
30
+ ### Screenshots or Additional Information:
19
31
 
20
- ## Possible Solution
21
- <!--- Not obligatory, but suggest a fix/reason for the bug, -->
32
+ [If applicable, add screenshots or other information to help illustrate the issue.]
22
33
 
23
- ## Steps to Reproduce
24
- <!--- Provide a link to a live example, or an unambiguous set of steps to -->
25
- <!--- reproduce this bug. Include code to reproduce, if relevant -->
26
- 1.
27
- 2.
28
- 3.
29
- 4.
34
+ ### Environment:
30
35
 
31
- ## Context (Environment)
32
- <!--- How has this issue affected you? What are you trying to accomplish? -->
33
- <!--- Providing context helps us come up with a solution that is most useful in the real world -->
36
+ - Operating System: [e.g., Windows, macOS, Linux]
37
+ - Browser (if applicable): [e.g., Chrome, Firefox, Safari]
38
+ - Version: [e.g., 1.0.0]
34
39
 
35
- <!--- Provide a general summary of the issue in the Title above -->
40
+ ### Checklist:
36
41
 
37
- ## Detailed Description
38
- <!--- Provide a detailed description of the change or addition you are proposing -->
42
+ - [ ] I have searched for a similar issue and didn't find any duplicates.
43
+ - [ ] I have included all the required information.
44
+ - [ ] I have tagged the issue with the label "bug."
39
45
 
40
- ## Possible Implementation
41
- <!--- Not obligatory, but suggest an idea for implementing addition or change -->
46
+ <!-- Feel free to add any additional details or context that might be helpful in resolving the issue. -->
@@ -0,0 +1,29 @@
1
+ ---
2
+ name: Documentation Issue
3
+ about: Report an issue with project documentation
4
+ title: "[DOCS] Briefly describe the documentation issue"
5
+ labels: documentation
6
+ assignees: ""
7
+ ---
8
+
9
+ ## Documentation Issue
10
+
11
+ ### Description:
12
+
13
+ [Provide a clear and concise description of the documentation issue.]
14
+
15
+ ### Affected Documentation:
16
+
17
+ [Specify the affected section(s) or page(s) of the documentation.]
18
+
19
+ ### Suggested Improvement:
20
+
21
+ [If you have a suggestion for improving the documentation, please describe it here.]
22
+
23
+ ### Checklist:
24
+
25
+ - [ ] I have searched for similar documentation issues and found none.
26
+ - [ ] I have included all the required information.
27
+ - [ ] I have tagged the issue with the label "documentation."
28
+
29
+ <!-- Feel free to add any additional details that might help in understanding or resolving the documentation issue. -->
@@ -1,20 +1,37 @@
1
1
  ---
2
- name: Feature request
3
- about: Suggest an idea for this project
4
- title: ''
5
- labels: ''
6
- assignees: ''
7
-
2
+ name: Feature Request
3
+ about: Suggest an idea for improvement
4
+ title: "[FEATURE] Briefly describe the feature request"
5
+ labels: enhancement
6
+ assignees: ""
8
7
  ---
9
8
 
10
- **Is your feature request related to a problem? Please describe.**
11
- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
9
+ ## Feature Request
10
+
11
+ ### Description:
12
+
13
+ [Provide a clear and concise description of the feature you're requesting.]
14
+
15
+ ### Use Case:
16
+
17
+ [Explain the use case or scenario where this feature would be beneficial.]
18
+
19
+ ### Proposed Solution:
20
+
21
+ [If you have a specific solution in mind, describe it here.]
22
+
23
+ ### Alternatives Considered:
24
+
25
+ [Have you considered any alternative solutions or workarounds?]
26
+
27
+ ### Additional Context:
28
+
29
+ [Add any additional context or information that might be relevant to the feature request.]
12
30
 
13
- **Describe the solution you'd like**
14
- A clear and concise description of what you want to happen.
31
+ ### Checklist:
15
32
 
16
- **Describe alternatives you've considered**
17
- A clear and concise description of any alternative solutions or features you've considered.
33
+ - [ ] I have searched for a similar feature request and didn't find any duplicates.
34
+ - [ ] I have included all the required information.
35
+ - [ ] I have tagged the issue with the label "enhancement."
18
36
 
19
- **Additional context**
20
- Add any other context or screenshots about the feature request here.
37
+ <!-- Feel free to add any other details that might help in understanding or implementing the requested feature. -->
@@ -0,0 +1,25 @@
1
+ ---
2
+ name: Question/Help
3
+ about: Ask a question or seek help
4
+ title: "[QUESTION] Briefly describe your question or issue"
5
+ labels: question
6
+ assignees: ""
7
+ ---
8
+
9
+ ## Question/Help
10
+
11
+ ### Description:
12
+
13
+ [Briefly describe the question or issue you need help with.]
14
+
15
+ ### Context:
16
+
17
+ [Provide any relevant context or details that might help others understand your question or issue better.]
18
+
19
+ ### Checklist:
20
+
21
+ - [ ] I have searched for similar questions or issues and found none.
22
+ - [ ] I have included all the required information.
23
+ - [ ] I have tagged the issue with the label "question."
24
+
25
+ <!-- Feel free to add any additional details that might help in addressing your question or issue. -->
@@ -0,0 +1,74 @@
1
+ ---
2
+ name: Report a security vulnerability
3
+ about: Report a security vulnerability to help us improve
4
+ title: "[SECURITY] Write a concise title here"
5
+ labels: security
6
+ assignees: ""
7
+ ---
8
+
9
+ <!-- If you believe you have found a security vulnerability in our project, please follow these steps to report it to us. We appreciate your efforts in disclosing the issue responsibly and will work with you to address the problem promptly. -->
10
+
11
+ # Security Vulnerability Report
12
+
13
+ ## Title:
14
+
15
+ [Concise title describing the vulnerability]
16
+
17
+ ## Contact Information:
18
+
19
+ [Your contact information - email or other preferred means of contact]
20
+ [Remember that this information may be publicly visible depending on the project's settings]
21
+
22
+ ## Description:
23
+
24
+ [Detailed description of the vulnerability, including steps to reproduce if possible]
25
+
26
+ ## Supporting Documentation:
27
+
28
+ [Attach any supporting documentation, code, or relevant information]
29
+
30
+ ## Impact:
31
+
32
+ [Describe the impact of the vulnerability]
33
+
34
+ ## Suggestions to Fix:
35
+
36
+ [If you have suggestions on how to fix the vulnerability, please include them here]
37
+
38
+ ## Steps to uncover:
39
+
40
+ [If you have suggestions on how to uncover the vulnerability, please include them here]
41
+
42
+ ## Steps to reproduce:
43
+
44
+ [If you have suggestions on how to reproduce the vulnerability, please include them here]
45
+
46
+ ## Severity:
47
+
48
+ [Low/Medium/High]
49
+
50
+ ## Affected Versions:
51
+
52
+ [List affected versions here]
53
+
54
+ ## Checklist:
55
+
56
+ - [ ] I have filled out all the fields above
57
+ - [ ] I have searched for a similar issue in the project and found none
58
+ - [ ] I have tagged the issue with the label "security"
59
+ - [ ] I understand that I may be contacted for further information and my contact information lies in the issue which may be publicly visible depending on the project's settings
60
+ - [ ] I understand and agree to license the code I am providing under the project's license
61
+
62
+ <!--
63
+ After creating the issue, tag it with the label "security". This will notify the project maintainers and we will respond as soon as possible.
64
+
65
+ Our Response: We will acknowledge your report as soon as possible and provide an estimated timeline for when you can expect a resolution.
66
+
67
+ Coordination: We will work with you to address the issue, and if necessary, coordinate the release of a fix.
68
+
69
+ Bounty: We do not offer a bounty for the disclosure of security vulnerabilities for public projects, but we will publicly thank you for your assistance unless you request to remain anonymous. If the project is private, we may offer a bounty at our discretion.
70
+
71
+ Code and License: The effective license for the code in the project is applied to the code provided by you in the report. If you provide a patch, you agree to license the code under the project's license.
72
+
73
+ Legal Safe Harbor: We will not take legal action against you or suspend your account if you follow the responsible disclosure process. We appreciate your assistance in helping us maintain the security of our project.
74
+ -->
@@ -0,0 +1,51 @@
1
+ ---
2
+ name: Translation Issue Report
3
+ about: Create a report to help us improve translations
4
+ title: "[TRANSLATION] Briefly describe the issue"
5
+ labels: translation
6
+ assignees: ""
7
+ ---
8
+
9
+ # Translation Issue Report
10
+
11
+ ## Description:
12
+
13
+ [Provide a clear and concise description of the translation issue.]
14
+
15
+ ## Context:
16
+
17
+ [Explain the context in which the translation issue occurred.]
18
+
19
+ ## Source Language:
20
+
21
+ [Specify the language of the original content.]
22
+
23
+ ## Target Language:
24
+
25
+ [Specify the language the content was translated into.]
26
+
27
+ ## Incorrect Translation:
28
+
29
+ [Provide the section or phrase that is incorrectly translated.]
30
+
31
+ ## Suggested Translation:
32
+
33
+ [Offer your suggested correction or improvement.]
34
+
35
+ ## Screenshots or Additional Information:
36
+
37
+ [If applicable, add screenshots or other information to help illustrate the translation issue.]
38
+
39
+ ## Environment:
40
+
41
+ - Operating System: [e.g., Windows, macOS, Linux]
42
+ - Browser (if applicable): [e.g., Chrome, Firefox, Safari]
43
+ - Version: [e.g., 1.0.0]
44
+
45
+ ## Checklist:
46
+
47
+ - [ ] I have searched for similar translation issues and didn't find any duplicates.
48
+ - [ ] I have included all the relevant information.
49
+ - [ ] I have tagged the issue with the label "translation."
50
+
51
+ <!-- Feel free to add any additional details or context that might be helpful in addressing the translation issue. -->
@@ -1,23 +1,52 @@
1
- * **Please check if the PR fulfills these requirements**
2
- - [ ] The commit message follows our guidelines
3
- - [ ] Tests for the changes have been added (for bug fixes / features)
4
- - [ ] Docs have been added / updated (for bug fixes / features)
1
+ <!--
2
+ The title of the GitHub must follow the following format:
3
+ [BUG/DOCS/FEATURE/SECURITY/TRANSLATION] Briefly describe the changes made in this pull request.
5
4
 
5
+ If your pull request doesn't fall under any of the above categories, please use the label "OTHER" and describe the changes in the title.
6
6
 
7
- * **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
7
+ For example:
8
+ [FEATURE] Add a new feature to the project
9
+ [BUG] Fix bug in the project
10
+ [DOCS] Update documentation
11
+ [SECURITY] Fix security vulnerability
12
+ [TRANSLATION] Translate content into a new language
13
+ [OTHER] Briefly describe the changes made in this pull request
8
14
 
15
+ A CLA is required for this pull request. Please read and sign the CLA at https://cla.developers.codevedas.com
16
+ -->
9
17
 
18
+ ## Pull Request
10
19
 
11
- * **What is the current behavior?** (You can also link to an open issue here)
20
+ ### Description:
12
21
 
22
+ [Provide a clear and concise description of the changes introduced by this pull request.]
13
23
 
24
+ ### Related Issue:
14
25
 
15
- * **What is the new behavior (if this is a feature change)?**
26
+ [If your pull request addresses a specific issue, reference it here by linking to the issue using the pound sign (#). For example, #123]
16
27
 
28
+ ### Proposed Changes:
17
29
 
30
+ [Outline the changes made in this pull request. Include any new features, bug fixes, or enhancements.]
18
31
 
19
- * **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
32
+ ### Checklist:
20
33
 
34
+ - [ ] I have tested these changes locally.
35
+ - [ ] I have ensured that my code follows the project's coding standards.
36
+ - [ ] I have updated the documentation (if applicable).
37
+ - [ ] I have added appropriate tests (if applicable).
38
+ - [ ] I have updated relevant comments in the code (if applicable).
39
+ - [ ] I have confirmed that the changes work with the latest version of dependencies.
40
+ - [ ] I have added appropriate labels to the pull request.
21
41
 
42
+ ### Screenshots or Additional Information:
22
43
 
23
- * **Other information**:
44
+ [If applicable, provide screenshots or any additional information that helps reviewers understand the changes.]
45
+
46
+ ### Environment:
47
+
48
+ - Operating System: [e.g., Windows, macOS, Linux]
49
+ - Browser (if applicable): [e.g., Chrome, Firefox, Safari]
50
+ - Version: [e.g., 1.0.0]
51
+
52
+ <!-- Feel free to add any additional details or context that might be helpful in reviewing the pull request. -->
@@ -4,7 +4,8 @@ updates:
4
4
  directory: "/"
5
5
  schedule:
6
6
  interval: "daily"
7
- - package-ecosystem: "npm"
7
+ - package-ecosystem: github-actions
8
8
  directory: "/"
9
9
  schedule:
10
- interval: "daily"
10
+ interval: daily
11
+ open-pull-requests-limit: 10
@@ -0,0 +1,148 @@
1
+ name-template: "v$RESOLVED_VERSION"
2
+ tag-template: "v$RESOLVED_VERSION"
3
+
4
+ autolabeler:
5
+ - label: "dependencies"
6
+ branch:
7
+ - /^dependabot\//
8
+ title:
9
+ - /^chore\(deps\):/
10
+ - /^chore\(dependencies\):/
11
+ - label: "feature"
12
+ branch:
13
+ - /^feat\//
14
+ title:
15
+ - /^feat:/
16
+
17
+ - label: "bug"
18
+ branch:
19
+ - /^bugfix\//
20
+ title:
21
+ - /^bugfix:/
22
+
23
+ - label: "docs"
24
+ branch:
25
+ - /^docs\//
26
+ title:
27
+ - /^docs:/
28
+
29
+ - label: "release"
30
+ branch:
31
+ - /^release\//
32
+ title:
33
+ - /^release:/
34
+
35
+ - label: "chore"
36
+ branch:
37
+ - /^chore\//
38
+ title:
39
+ - /^chore:/
40
+
41
+ - label: "refactor"
42
+ branch:
43
+ - /^refactor\//
44
+ title:
45
+ - /^refactor:/
46
+
47
+ - label: "test"
48
+ branch:
49
+ - /^test\//
50
+ title:
51
+ - /^test:/
52
+
53
+ - label: "style"
54
+ branch:
55
+ - /^style\//
56
+ title:
57
+ - /^style:/
58
+
59
+ - label: "ci"
60
+ branch:
61
+ - /^ci\//
62
+ title:
63
+ - /^ci:/
64
+
65
+ - label: "perf"
66
+ branch:
67
+ - /^perf\//
68
+ title:
69
+ - /^perf:/
70
+
71
+ - label: "build"
72
+ branch:
73
+ - /^build\//
74
+ title:
75
+ - /^build:/
76
+
77
+ categories:
78
+ - title: "๐Ÿš€ Features"
79
+ labels:
80
+ - "feature"
81
+
82
+ - title: "๐Ÿ› Bug Fixes"
83
+ labels:
84
+ - "bug"
85
+
86
+ - title: "๐Ÿ“ Documentation"
87
+ labels:
88
+ - "docs"
89
+
90
+ - title: "๐Ÿ”– Releases"
91
+ labels:
92
+ - "release"
93
+
94
+ - title: "๐Ÿงฐ Maintenance"
95
+ labels:
96
+ - "chore"
97
+ - "refactor"
98
+ - "dependencies"
99
+
100
+ - title: "๐Ÿงช Tests"
101
+ labels:
102
+ - "test"
103
+
104
+ - title: "๐Ÿ’… Styling"
105
+ labels:
106
+ - "style"
107
+
108
+ - title: "โš™๏ธ CI"
109
+ labels:
110
+ - "ci"
111
+
112
+ - title: "๐Ÿš€ Performance"
113
+ labels:
114
+ - "perf"
115
+
116
+ - title: "๐Ÿ“ฆ Build"
117
+ labels:
118
+ - "build"
119
+
120
+ change-template: "- $TITLE @$AUTHOR (#$NUMBER)"
121
+ no-changes-template: "- No user-facing changes."
122
+
123
+ version-resolver:
124
+ major:
125
+ labels:
126
+ - "breaking"
127
+ minor:
128
+ labels:
129
+ - "feature"
130
+ patch:
131
+ labels:
132
+ - "bug"
133
+ - "chore"
134
+ - "refactor"
135
+ - "test"
136
+ - "style"
137
+ - "ci"
138
+ - "perf"
139
+ - "build"
140
+ - "dependencies"
141
+
142
+ exclude-labels:
143
+ - "skip-changelog"
144
+
145
+ template: |
146
+ ## Changes
147
+
148
+ $CHANGES
@@ -0,0 +1,45 @@
1
+ name: Pull Requests
2
+ on:
3
+ push:
4
+ branches: [main]
5
+ pull_request:
6
+ branches: [main]
7
+ jobs:
8
+ lint:
9
+ runs-on: ubuntu-latest
10
+ steps:
11
+ - name: Checkout code
12
+ uses: actions/checkout@v5
13
+
14
+ - name: Set up Ruby
15
+ uses: ruby/setup-ruby@v1
16
+ with:
17
+ ruby-version: 3.4.3
18
+ bundler-cache: true
19
+
20
+ - name: Lint code for consistent style
21
+ run: bin/rubocop -f github
22
+ test:
23
+ runs-on: ubuntu-latest
24
+ steps:
25
+ - name: Install packages
26
+ run: sudo apt-get update && sudo apt-get install --no-install-recommends -y build-essential git libyaml-dev pkg-config
27
+
28
+ - name: Checkout code
29
+ uses: actions/checkout@v5
30
+
31
+ - name: Set up Ruby
32
+ uses: ruby/setup-ruby@v1
33
+ with:
34
+ ruby-version: 3.4.3
35
+ bundler-cache: true
36
+
37
+ - name: Run tests
38
+ run: bin/rspec --format documentation --color --profile
39
+
40
+ - name: Upload simplecov report
41
+ uses: actions/upload-artifact@v4
42
+ with:
43
+ name: simplecov-report
44
+ path: ${{ github.workspace }}/coverage
45
+ if-no-files-found: ignore