fix: commit message dissappears #33473
Closed
+115
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brayn003
changed the title
brayn003
added
Git Version Control
github-actions
bot
added
Frontend
2 tasks
brayn003
added
ok-to-test
…mmit-message-dissappears
brayn003
added
ok-to-test
|
This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected. |
|
This PR has been closed because of inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR for running tests for forked PR #33096
Fixes #24988
Automation
/ok-to-test tags="@tag.Git"
🔍 Cypress test results
Caution
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9106942629
Commit: 3ca93c1
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:
- cypress/e2e/Regression/ClientSide/BugTests/GitBugs_Spec.ts
- cypress/e2e/Regression/ClientSide/Git/GitSync/DeleteBranch_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitSync/Deploy_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitSync/GitBugs_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitSync/GitStatusLite_spec.ts
- cypress/e2e/Regression/ClientSide/Git/GitSync/GitSyncedApps_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitSync/MergeViaRemote_spec.ts
- cypress/e2e/Regression/ClientSide/Git/GitSync/Merge_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitSync/SwitchBranches_spec.js
- cypress/e2e/Regression/ClientSide/Git/GitWithJSLibrary/GitwithCustomJSLibrary_spec.js
To know the list of identified flaky tests - Refer hereCommunication
Should the DevRel and Marketing teams inform users about this change?