We've noticed something weird at my job. In Stash, when looking at the public repository list, some users appear as:
Jane Doe / super-app
While others appear as just
Is this controlled by a setting of some kind? It's always the former in the case of a real project.
It should always appear as "Project / Repository" where project may be a user who has forked. From your example above I would guess that "Jane Doe" the user has forked super-app? Is there no project listed for 'super-app' in the second example.
There's certainly no configuration around the displaying of this information.
Ok, well I feel a little bit better. Yes, right now we have 11 people evaluating git/stash. Of the 11, all of the projects (there's only 2 projects) and 3 of the 11 developers show up like this. All others show up as just the repository name.
We're on Stash 2.6.3 if it helps.
Looking at the code I don't see how that's possible. Sorry if this is a dumb question - we are just talking about the public repository page right? Certainly if you're looking at repositories in the project page you'll just see the name.
Can you look at the HTML of that page? It's easier if you use Chrome/Firefox, right-click and inspect element. I would except to see something like this for a single row:
<td> <span class="project-name"> <span class="aui-avatar aui-avatar-small aui-avatar-project"> <span class="aui-avatar-inner"> <img src="/projects/TEST/avatar.png?s=48" alt="Test"> </span> </span> <a href="/projects/TEST" title="Test">Test</a> </span> <span class="repository-name"> <a href="/projects/TEST/repos/my-repo/browse">my-repo</a> </span> </td>
What do you see for the row that is missing the project name? Is the project-name span there?
I feel like I'm missing something here. Let me know what you find.
Sure, I hope you don't mind the names have been changed to protect the innocent. Both of these are forks of the same repository, yet the generated HTML is very different.
One thought I had, we're using Crowd for authentication.
<!-- wrong html --> <tr><td><span class="repository-name"><span class="aui-icon aui-icon-small aui-iconfont-devtools-repository-forked" title="This repository is a fork of MainProject/super-app">Fork</span><a href="/users/ba.baracus/repos/super-app/browse">super-app</a></span></td></tr> <!-- right html --> <tr><td><span class="project-name"><span class="aui-avatar aui-avatar-small"><span class="aui-avatar-inner"><img src="http://www.gravatar.com/avatar/gravatar.jpg?s=48&amp;d=mm" alt="Hannibal Lecter"></span></span><a href="/users/hannibal.lecter" title="Hannibal Lecter">Hannibal Lecter</a></span><span class="repository-name"><a href="/users/hannibal.lecter/repos/super-app/browse">super-app</a></span></td></tr>
So you've found a bug I'm afraid (and it looks like I broke it fixing something else). :(
It looks like any repositories that are lazily loaded (ie after the 25th one) will be missing the project.
I've already fixed the issue, but I couldn't say whether it will be available in a bugfix release for 2.7 or 2.8. Please watch that issue for more updates.
Apologoes for any inconvenience.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot