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

[Bug]: Discard and pull the “JIT pull” changes doesn’t trigger another “JIT pull” #38551

Open
1 task done
subrata71 opened this issue Jan 9, 2025 · 0 comments
Open
1 task done
Assignees
Labels
Bug Something isn't working Low An issue that is neither critical nor breaks a user flow Needs Triaging Needs attention from maintainers to triage Packages & Git Pod All issues belonging to Packages and Git Packages Pod issues that belong to the packages pod Release

Comments

@subrata71
Copy link
Contributor

subrata71 commented Jan 9, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Description

When a developer wants to pull new developments from the remote repo, they want to get as reference the latest published state of each package so that they can ensure they are developing on top of a valid reference to the packages used

https://www.notion.so/appsmith/Discard-and-pull-the-JIT-pull-changes-doesn-t-trigger-another-JIT-pull-175fe271b0e28040a3bee511a99e316b

Steps To Reproduce

Steps to Reproduce the Bug:

  1. Create a JS module instance with one function in a Git-connected app.
  2. Navigate to the package editor.
  3. Add another function to the same JS module.
  4. Publish the package.
  5. Open the consuming app in Edit mode.
  6. Trigger a JIT pull.
  7. Verify that the existing JS module instance shows both JS functions.
  8. Discard the changes and pull from the remote.
  9. Note that the newly added JS function is missing from the JS module instance.
  10. Reload the page.
  11. Observe that no JIT pull is triggered, which indicates a bug.

Public Sample App

No response

Environment

Production

Severity

Low (Cosmetic UI issues)

Issue video log

No response

Version

Self Hosted

@subrata71 subrata71 added Bug Something isn't working Needs Triaging Needs attention from maintainers to triage labels Jan 9, 2025
@subrata71 subrata71 self-assigned this Jan 9, 2025
@Nikhil-Nandagopal Nikhil-Nandagopal added Low An issue that is neither critical nor breaks a user flow Production labels Jan 9, 2025
@subrata71 subrata71 added Release Packages Pod issues that belong to the packages pod and removed Production labels Jan 9, 2025
@github-actions github-actions bot added the Packages & Git Pod All issues belonging to Packages and Git label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Low An issue that is neither critical nor breaks a user flow Needs Triaging Needs attention from maintainers to triage Packages & Git Pod All issues belonging to Packages and Git Packages Pod issues that belong to the packages pod Release
Projects
None yet
Development

No branches or pull requests

2 participants