git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brooke Kuhlmann <brooke@alchemists.io>
To: git@vger.kernel.org
Subject: Git Commit Notes (fetching/pushing)
Date: Sun, 6 Aug 2023 12:35:50 -0600	[thread overview]
Message-ID: <D01976C3-4B91-464B-ACF0-78DFFB066747@alchemists.io> (raw)

I'm noticing issues with GitHub and GitLab when fetching and pushing commit notes and wanted to know if there is a correct way to configure my Git configuration for working with these servers (or maybe notes aren't supported at al)?

Here's my configuration:

```
[notes]
  rewriteRef = refs/notes/commits

[remote "origin"]
  fetch = +refs/notes/*:refs/notes/*
  push = +refs/notes/*:refs/notes/*
```

Upon creating a note (i.e. `git notes add`) and then pushing changes to the remote, I'll see the following response from GitHub:

``` 
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 289 bytes | 289.00 KiB/s, done.
Total 2 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To https://github.com/bkuhlmann/test
   5811bd44c32b..0f2422597c5d  refs/notes/commits -> refs/notes/commits
```

Only problem is the notes are not pushed. In fact, the feature branch I'm working is never updated. Only when removing my `[remote "origin"]` Git configuration does the GitHub server work properly (i.e. my changes are pushed to the remote server...but without any notes). Strangely, in all cases GitHub answers back with a success message even though that is incorrect.

Anyway, if anyone has advice or additional information how this should work (or if my configuration is wrong), I'd be grateful. 🙇🏻‍♂️





             reply	other threads:[~2023-08-06 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 18:35 Brooke Kuhlmann [this message]
2023-08-06 20:09 ` Git Commit Notes (fetching/pushing) Taylor Blau
2023-08-06 21:49   ` Brooke Kuhlmann
2023-08-07  1:07     ` Junio C Hamano
2023-08-07 14:02       ` Brooke Kuhlmann
2023-08-07 16:14         ` Junio C Hamano
2023-08-07 20:18           ` Brooke Kuhlmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D01976C3-4B91-464B-ACF0-78DFFB066747@alchemists.io \
    --to=brooke@alchemists.io \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).