Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: added fix for commit messages #39134

Open
wants to merge 1 commit into
base: release
Choose a base branch
from

Conversation

sondermanish
Copy link
Contributor

@sondermanish sondermanish commented Feb 7, 2025

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #39115

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.Git"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13199336570
Commit: 62eff0c
Cypress dashboard.
Tags: @tag.Git
Spec:


Fri, 07 Feb 2025 14:07:19 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Refactor
    • Streamlined how commits are processed by sending only the essential information in each request.
    • Adjusted the parameter handling for commit actions to ensure a more consistent and efficient operation.

@sondermanish sondermanish self-assigned this Feb 7, 2025
Copy link
Contributor

coderabbitai bot commented Feb 7, 2025

Walkthrough

This update refines the commit request process in the git module. The commitRequestOld function now constructs a payload that includes only the commitMessage and doPush fields rather than the entire params object. Additionally, the commitRequest function has been updated to reflect the new parameter name (changed from branchedApplicationId to refArtifactId) in commitRequestOld. The control flow based on the isNew flag remains unchanged.

Changes

File Change Summary
app/client/src/git/requests/commitRequest.ts • Modified commitRequestOld to construct a payload with only commitMessage and doPush instead of the full params object.
• Renamed first parameter from branchedApplicationId to refArtifactId.
• Updated commitRequest and commitRequestNew usage to align with the new signature.

Sequence Diagram(s)

sequenceDiagram
    participant C as Caller
    participant CR as commitRequest
    participant CO as commitRequestOld
    participant CN as commitRequestNew
    participant API as Api.post

    C->>CR: commitRequest(artifactType, refArtifactId, params, isNew)
    alt isNew true
        CR->>CN: commitRequestNew(artifactType, refArtifactId, params)
        CN->>API: Api.post(filtered payload)
    else isNew false
        CR->>CO: commitRequestOld(refArtifactId, params)
        Note right of CO: Constructs payload with commitMessage & doPush
        CO->>API: Api.post(filtered payload)
    end
Loading

Possibly related PRs

Suggested labels

Bug, ok-to-test, Widgets Product, Query & Widgets Pod

Suggested reviewers

  • AmanAgarwal041
  • abhvsn

Poem

In lines of code, a change takes flight,
A refined commit in gentle light.
Parameters trimmed with care so neat,
Branching flows now smooth and sweet.
Code sings its tale — a joyful feat!
🚀✨

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sondermanish
Copy link
Contributor Author

/build-deploy-preview skip-tests=true

@github-actions github-actions bot added the Bug Something isn't working label Feb 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/13199264265.
Workflow: On demand build Docker image and deploy preview.
skip-tests: true.
env: ``.
PR: 39134.
recreate: .

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
app/client/src/git/requests/commitRequest.ts (1)

31-41: Ensure parameter naming consistency across functions

The main function uses refArtifactId but passes it to commitRequestOld which expects branchedApplicationId. While this works functionally, the parameter naming should be consistent.

Consider updating the parameter names to be consistent across all functions:

-async function commitRequestOld(
-  branchedApplicationId: string,
+async function commitRequestOld(
+  refArtifactId: string,
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ac41ad2 and 62eff0c.

📒 Files selected for processing (1)
  • app/client/src/git/requests/commitRequest.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: client-lint / client-lint
  • GitHub Check: client-prettier / prettier-check
  • GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-build / client-build
🔇 Additional comments (2)
app/client/src/git/requests/commitRequest.ts (2)

10-13: Parameter name inconsistency with AI summary

The AI summary indicates the parameter name was changed to refArtifactId, but the implementation still uses branchedApplicationId. This inconsistency should be addressed.

Please clarify if the parameter name should be updated to match the summary.


14-17: LGTM! Improved payload structure

Good improvement to only send the required fields (commitMessage and doPush) instead of the entire params object.

@sondermanish sondermanish requested a review from brayn003 February 7, 2025 11:56
@sondermanish sondermanish added the ok-to-test Required label for CI label Feb 7, 2025
@github-actions github-actions bot added Git Product Issues related to version control product Needs Triaging Needs attention from maintainers to triage Packages & Git Pod All issues belonging to Packages and Git Release Blocker This issue must be resolved before the release labels Feb 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

Deploy-Preview-URL: https://ce-39134.dp.appsmith.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Git Product Issues related to version control product Needs Triaging Needs attention from maintainers to triage ok-to-test Required label for CI Packages & Git Pod All issues belonging to Packages and Git Release Blocker This issue must be resolved before the release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: commit messages added from application side are not reflected on GIT repo
2 participants