I recently started to use GitHub Mylyn connector for Eclipse and I have it working, I create new tasks and I can see them in Eclipse and GitHub.
The problem is when me or someone else create an Issue on GitHub I can't see it on Eclipse. I have done this and configured Mylyn on that way as you can see in the image:
But as you can see under "Bugs and Enhancements" I have nothing and here I actually have one issues, so, why don't they appear? Is something to do with the fields Assigned to and Mentioning ? I have filled both with my GitHub username, then only one but with no results.
I was also having same problem. The problem here is that the Labels which are checked have And relationship rather than Or relationship, i.e if you check both bug and enhancement only the tasks that are labelled both bug and enhancements will show up there.
So, I think it will work if create separate query for enhancements and bugs.
Related
I am not by any means a sophisticated github user. I have learned the minimum handful of commands needed to add, commit, and push my project code to the public github.com repository. So far it's been working fairly well... until today when I tried to create a new release (my third).
For some reason, when I try to publish my new release, I get the message
Tag could not be created. Pre-receive hooks failed.
I have never seen this message before.
I have tried various different tag names; I have tried logging out and back in again; I have tried pre-tagging on my local disk copy of the repo; I have pushed and pulled (both ends are up to date). This about exhausts my repertoire of things to try :-(
As a relative n00b I find this message incredibly opaque (sigh). I have tried googling for it, but quickly got in over my head -- most of the hits I found were discussions about people setting up their own networked repos and installing or tweaking their own custom "pre-receive hooks", whereas I am just a dumb user of github.com apparently struggling with whatever "pre-receive hooks" they have installed (?). If anyone can at least point me in the right direction I'd be most grateful.
Make sure you select the tag version in the dropdown. The GitHub form will let you submit when this field is blank, but it will always display the mentioned error message. (You do not need a 'v' prefix.).
The latest Github form makes this more cryptic by having a dropdown titled 'Tag:Choose or Create" that hides the fact that this field is both required but not set.
Latest Github Form
Older Github Form
In a GitHub context, I have seen that error message in this issue
It could be a tag naming convention issue.
The GitHub release documentation recommends (enforces?) a tag following the semantic versioning naming scheme: vX.Y.Z.
As shown here, try vx.y.z.
It would be really great to have a Github issue be in an intermediary "Resolved" state before I close the issue.
Right now, I have a "Resolved" label and I manually select the issue and change it's label on the web after I commit. Is there a way I can do this from the commit message?
I am sure this is a common problem. How do you guys solve this?
I have never used Github API but can this be done using the API If I were to do this myself?
Since September 14, 2016 you could manage your states with projects. See image below:
Reference and source: GitHub - A whole new GitHub Universe: announcing new tools, forums, and features.
I know it's not like a new state like "needs verification" because you can't like #NevikRehnel said in his answer. But you could make a column named "open", "needs verification" and "closed" and all the issues can you list in correct column.
No, Github issues only support two states (open and closed). Any other "states" must be realized via labels, as you are already doing right now.
And as of right now, there is no way to apply labels from commit messages.
You can always request such features from Github support of course, and they might be implemented at some point.
You can manage this problem using this method : Adding and reassigning github issues via commit message.
A simple ruby script will run on each commit, and check the commit message looking for ~myLabel and =assignedMember to update correctly the issue.
So I've recently started using Mylyn at my company, love it personally and works great with Jira. However now I'm trying to get it working on Github for personal projects that I work on with several other people.
I'm using Eclipse Juno with the Github connector and added the repository information. When I go create a task, it correctly does so and does pull the tags that I have configured correctly, so I know it has good connectivity both ways. When I save the task in Mylyn it will show up on Github just fine.
The problem is, I need access to issues that others create on Github, but when I create a Query in Mylyn and name it ( Say "All Bugs" ), then choose the bug labels and hit finish it shows the query in the Task view, however it is empty and never retrieves the list of Issues from Github. I know their there, it's just not showing them in Mylyn, and Mylyn isn't throwing any errors.
I've also tried a Query with all the above and "Mention" field with my name( just in case the blank fields were messing with the query ) however that didn't work either.
One thing to note, I'm using this on a Private repo, but doing searching( and as evidence that I can fetch labels and push issues ) I don't think private Vs public repos are an issue here.
Really hope someone can lend a hand. Thanks
#TheKojuEffect answered this one for me here:
Why Mylyn is not getting issues from GitHub?
Basically, if you select more than one label in your query in Eclipse, the query will only pull the issues with ALL of those labels (Logical AND, as opposed to the OR that I was expecting). Create a query for each of the issue labels you'd like to see.
The best approach to this is to open a bug report against Github connector for Mylyn.
I have started to use Cloud9 IDE recently and have to say I really like it as an individual. I use VS 2010 at work and TFS 2010 too. This made me think about the TFS equivalent for Cloud9. GitHub is something I have always been aware of but never really used.
I have done my research and read docs etc, what I really need some clarification in though is the whole Work Item system. I know GitHub has an Issue tracking but does it have a Work Item system similar to TFS. With the main features such as assigning work items to developers?
A little explanation to just clarify would be fantastic. Thanks!
If you're looking for a way to have Issues show up like WorkItems in your task list in visual studio, I don't think there is a solution for this to date.
You can however assign developers to issues within GitHub:
Create or Edit an Issue
Click the gear next to "No one is assigned".
Select a member from your organization to assign the issue to them.
I just want to know if the search result in eclipse search view can be shared with fellow team mate as it is.
I perform a search and delete few unwanted entries and then send it to him/ her
The other person shall be able to view it exactly same manner in the search view.
Is there a way to do this?
The will be very helpful for me
You should be looking at the Mylyn project (http://eclipse.org/mylyn).
This project allows you to create tasks and send them to co-workers through a task repository (such as bugzilla, jira, or most major issue trackers). Attached to these tasks are "contexts", which associate code elements (methods, fields, classes, etc) with the task.
Here is what you would need to do:
Install mylyn (you and all co-workers)
Install the proper connector for your issue tracker (most major issue trackers have one). If you are not using an issue tracker, then you can still import and export tasks as files, but it is less easy to do, and I'd recommend using an issue tracker anyway.
Now add the task repository to your Eclipse. This is the way that mylyn speaks to your issue tracker. It allows you to create issues, bug reports, tasks, etc, from within Eclipse.
With this set up, you can now create a task associated with a task repository and activate it. You can add the desired program elements to your task by right clicking -> Mark as Landmark.
Once you have your task context complete, you can then attach the context to the remote repository (essentially attaching a zip file to the issue in your issue tracker). Other users can then retrieve the context and immediately start working with the context that you created.
It is really a great way to work when you need to share information about specific features in the code to other people on the project.