diff --git a/.github/workflows/convert-pull-request-title.yml b/.github/workflows/convert-pull-request-title.yml index 6d00ac9..63c5eb9 100644 --- a/.github/workflows/convert-pull-request-title.yml +++ b/.github/workflows/convert-pull-request-title.yml @@ -1,4 +1,4 @@ -name: Convert Pull Req Title Into Conventional Commit Scheme +name: Convert Pull Req Title Into Conventional Commit Scheme! on: pull_request: diff --git a/.gitignore b/.gitignore index 3b23008..05d7388 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,3 @@ -### Node ### +# Node # node_modules package-lock.json \ No newline at end of file diff --git a/LICENSE b/LICENSE index 4b9310e..dc8c678 100644 --- a/LICENSE +++ b/LICENSE @@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. +SOFTWARE. \ No newline at end of file diff --git a/README.md b/README.md index 09eb25a..6574fc0 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ -## 🌟 -# convert_pull_req_title_into_conventional_commit_scheme +## 🌟🌟🌟 +# **convert_pull_req_title_into_conventional_commit_scheme** > [!NOTE] > The [**`convert_pull_req_title_into_conventional_commit_scheme`**](https://github.com/marketplace/actions/convert-pull-request-title-into-conventional-commit-scheme) project is a public **GitHub Action** available in the GitHub Marketplace. By utilizing this action, users can automatically **convert new pull request titles into the conventional commits format** as defined by [conventionalcommits.org](https://www.conventionalcommits.org/). diff --git a/action.yml b/action.yml index 18d9c03..e568128 100644 --- a/action.yml +++ b/action.yml @@ -1,4 +1,4 @@ -name: Convert Pull Req Title Into Conventional Commit Scheme +name: Convert Pull Req Title Into Conventional Commit Scheme! description: By utilizing this action, users can automatically convert new pull request titles into the conventional commits format author: ArnavK-09 diff --git a/dist/index.js b/dist/index.js index 2514eb0..4259897 100644 --- a/dist/index.js +++ b/dist/index.js @@ -31728,7 +31728,7 @@ const prompt = (title, description, include_emoji = false) => { return ` # Give me conventional commit message following www.conventionalcommits.org for pull request with title and description mentioned above. Only in single Line. ## ${include_emoji ? "ALSO INCLUDE appropriate EMOJI IN STARTING OF COMMIT message" : ""} - + # Documentation for conventionalcommits.org: The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. @@ -31826,7 +31826,6 @@ const initAction = async () => { const result = await gemini.generateContent( prompt(prTitle, prDescription, includeEmoji), ); - core.notice(`Prompt:- ${prompt(prTitle, prDescription, includeEmoji)}`) /** * Manipulating response into string @@ -31857,7 +31856,6 @@ const initAction = async () => { }; // Call the action -core.debug(`Github Payload: ${github.context}`); initAction(); })(); diff --git a/index.js b/index.js index ff077bd..71b2371 100644 --- a/index.js +++ b/index.js @@ -14,7 +14,7 @@ const prompt = (title, description, include_emoji = false) => { return ` # Give me conventional commit message following www.conventionalcommits.org for pull request with title and description mentioned above. Only in single Line. ## ${include_emoji ? "ALSO INCLUDE appropriate EMOJI IN STARTING OF COMMIT message" : ""} - + # Documentation for conventionalcommits.org: The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. @@ -112,7 +112,6 @@ const initAction = async () => { const result = await gemini.generateContent( prompt(prTitle, prDescription, includeEmoji), ); - core.notice(`Prompt:- ${prompt(prTitle, prDescription, includeEmoji)}`) /** * Manipulating response into string @@ -143,5 +142,4 @@ const initAction = async () => { }; // Call the action -core.debug(`Github Payload: ${github.context}`); initAction(); diff --git a/package.json b/package.json index 4473c22..257f7c5 100644 --- a/package.json +++ b/package.json @@ -9,14 +9,14 @@ "keywords": [ "github-action", "commitconventions", - "gemini-pro" + "gemini-pro", + "utils" ], "author": "ArnavK-09", "license": "MIT", "dependencies": { "@actions/core": "^1.10.1", "@actions/github": "^6.0.0", - "@google/generative-ai": "^0.2.0", - "@vercel/ncc": "^0.38.1" + "@google/generative-ai": "^0.2.0" } }