-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
comment adds new comment with every commit #145
Comments
Any screenshot? Should be related to #138 or #143(most likely) cc @alan910127 |
Hello @maxkarkowski, are you upgraded from v0.11.0 or v0.10.x? |
hey @alan910127 sorry of course i can. we are currently on version 0.10.3 Update: |
|
Hey @maxkarkowski, I couldn't reproduce the error on a project created on Here's something I think might be relevant:
|
@alan910127 I have the same problem, we are using a self-hosted instance of GitLab if that helps, but when I tested on |
we are also using a self hosted gitlab |
this is the comment job we have . it runs on every merge request
|
Got it. I will try to spin up a self-hosted GitLab instance and test the issue inside that. |
ist GitLab Community Edition v16.6.0 |
@JounQin I have found that the Reverting #143 could solve the Update: Using |
close #145 --------- Co-authored-by: JounQin <[email protected]>
@maxkarkowski @idumancic It should be fixed in version |
didnt fix it for me :/ |
@maxkarkowski Please provide more details, such as GitLab instance version? |
it is still GitLab Community Edition v16.6.0. ;) i just updated to the newest version of changesets-gitlab. the pipeline then executes |
I'm a bit hesitant to admit this, but I'm having difficulty configuring a GitLab CE instance in a newer version with runners correctly. Would anyone be willing to grant me access to their GitLab instance so that I can test for the issue? |
sorry for the inconvenience but i cannot share my gitlab instance because it is owned by customer with very sensitive data |
@alan910127 Just wanted to tell you that it's fixed for me, it only generates one comment. Sorry for being so late to respond, honestly I forgot about it. |
that is weird. can you maybe share what command you execute in your pipeline? i still get multiple comments :/ |
@maxkarkowski Maybe you can help to use |
what exactly should i do with patch package? run it before changesets-gitlab on my pipeline? i use pnpm so i can only use pnpm patch. |
Thanks that you're willing to help for debugging. You can try to patch Mostly you should add some logs at the following: changesets-gitlab/src/comment.ts Lines 107 to 132 in 9c6e792
So that we can check why the previous mr was not found. After seeing |
Seems like I'm too late, sorry about that 😅. |
@alan910127 Never mind. You can still help to review it to prevent unexpected regressions or bugs. |
i am sorry to say it but i installed the newest version and still get multiple comments |
@maxkarkowski 🤣 Let's debug again. |
what can i do? |
@maxkarkowski As previous, add log at changesets-gitlab/src/comment.ts Lines 122 to 132 in 99d8c17
|
if i use pnpm patch i pnly have the compiled js file. i'll try to add some console.logs |
i added some console.logs like this. and the result is
|
|
so without a gitlab_user_name? |
yep
|
i altered the name to GITLAB_CI_USER_NAME_BKP . still got a new comment |
and the next commit
|
@maxkarkowski You'd better to log |
result -->
and again with GITLAB_CI_USER_NAME (just to test it)
|
- note.body.includes(generatedByBotNote);
+ return note.body.includes(generatedByBotNote); |
is this an bug i added by rewriting the function? :D |
Yes, |
damn it. okay. i now created a new MR in my repo with the newest version of changesets-gitlab. and i altered the gitlab_ci_user_name to the group_114_bot_random-hash user. now i will give it another try |
You just need to remove |
now it works. sorry for the inconvience. but also thanks for your quick response and your help debugging it. |
OK, we can finally close this issue, right? It's still worth to add a section of doc to describe this issue when using with |
since we updated changesets-gitlab we have now the issue that with every commit the changesets-gitlab comment command creates a new comment in our merge request. before the update it only created one comment for a merge request.
The text was updated successfully, but these errors were encountered: