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

Two work items were created for the same GitHub issue #97

Closed
edmorley opened this issue Sep 1, 2020 · 4 comments
Closed

Two work items were created for the same GitHub issue #97

edmorley opened this issue Sep 1, 2020 · 4 comments

Comments

@edmorley
Copy link
Member

edmorley commented Sep 1, 2020

Hi!

I created heroku/heroku-buildpack-python#1060 and then added the gus: story GitHub label that I've set up to be for User Stories.

The Git2Gus bot then successfully created:
https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07B0000008XaA0IAK/view

A few minutes later I added another label to the GitHub issue, at which point Git2Gus unexpectedly created a second unwanted User Story:
https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07B0000008XaAnIAK/view

It's not clear why this occurred.

The config for the repo in question is here:
https://github.com/heroku/heroku-buildpack-python/blob/ab69658efbdb3addf7b2e155ebb5bb6e518a597c/.git2gus/config.json

@edmorley
Copy link
Member Author

This happened again in:
heroku/heroku-buildpack-python#1067

This issue makes Git2Gus pretty unusable right now unfortunately - since it appears I can't add any additional labels without causing duplicates.

@edmorley
Copy link
Member Author

Both of the work items contain the correct related URL for what it's worth:

$ sfdx force:data:record:get -s ADM_Work__c -i a07B0000008dLYJIA2 --json | jq '.result.Related_URL__c'
"https://github.com/heroku/heroku-buildpack-python/issues/1067"

$ sfdx force:data:record:get -s ADM_Work__c -i a07B0000008dLYdIAM --json | jq '.result.Related_URL__c'
"https://github.com/heroku/heroku-buildpack-python/issues/1067"

@edmorley
Copy link
Member Author

Any news on this? I've stopped using Git2Gus because of this issue.

@lpomerleau
Copy link

Following this issue. I am seeing the same on these repos:

edmorley added a commit to heroku/heroku-buildpack-python that referenced this issue Jan 29, 2021
Since the Git2GUS tool has a number of bugs/deficiencies which mean it's
not usable for the time being. If that changes in the future we can add
this configuration back and re-evaluate.

For example:
- forcedotcom/git2gus#97
- forcedotcom/git2gus#90
- forcedotcom/git2gus#91
- forcedotcom/git2gus#92
- forcedotcom/git2gus#86
- forcedotcom/git2gus#15

Closes W-8825462.

[skip changelog]
edmorley added a commit to heroku/heroku-buildpack-python that referenced this issue Jan 30, 2021
Since the Git2GUS tool has a number of bugs/deficiencies which mean it's
not usable for the time being. If that changes in the future we can add
this configuration back and re-evaluate.

For example:
- forcedotcom/git2gus#97
- forcedotcom/git2gus#90
- forcedotcom/git2gus#91
- forcedotcom/git2gus#92
- forcedotcom/git2gus#86
- forcedotcom/git2gus#15

Closes W-8825462.

[skip changelog]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants