Claude not pushing a commit to remote branch

Resolved 💬 2 comments Opened Feb 26, 2025 by MarcusElwin Closed Feb 26, 2025

First of all great feature! I tried to use it to update some entities and my gcl schema for a PR I was working on:

Bash(git commit -m "fix: remove redundant field decorators from timestamp fields    …

      - Remove duplicate @Field decorators from timestamp fields that should be hidden
      - Keep only @HideField decorator to ensure fields don't appear in GraphQL schema
      - Remove unused GraphQLDateTime imports

      🤖 Generated with Claude Code
      Co-Authored-By: Claude <noreply@anthropic.com>")
  ⎿  [chore/update-create-pb-to-do-upsert 889af8d] fix: remove redundant field decorators from timestamp fields
      4 files changed, 3 insertions(+), 15 deletions(-)
  ⎿  [STARTED] Backing up original state...
     [COMPLETED] Backed up original state in git stash (329dc40)
     [STARTED] Running tasks for staged files...
     [STARTED] package.json — 4 files
     [STARTED] *.{ts,tsx} — 3 files
     [STARTED] *.{ts,tsx,js,jsx,json,md} — 3 files
     [STARTED] eslint --cache --fix
     [STARTED] prettier --write
     [COMPLETED] prettier --write
     [COMPLETED] *.{ts,tsx,js,jsx,json,md} — 3 files
     [COMPLETED] eslint --cache --fix
     [COMPLETED] *.{ts,tsx} — 3 files
     [COMPLETED] package.json — 4 files
     [COMPLETED] Running tasks for staged files...
     [STARTED] Applying modifications from tasks...
     [COMPLETED] Applying modifications from tasks...
     [STARTED] Cleaning up temporary files...
     [COMPLETED] Cleaning up temporary files...

⏺ Bash(git status)…
  ⎿  On branch chore/update-create-pb-to-do-upsert
     nothing to commit, working tree clean

⏺ Fixed the issue with redundant field decorators and committed the changes. The timestamp fields will now be:
  1. Available in the database through TypeORM
  2. Hidden from the GraphQL schema (using only @HideField)
  3. No longer have redundant @Field decorators

The commit and fixes where create but I had to do the actual git push is this intended behaviour?

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗