Is there a way to create a link that filters a github organizations by topic? Under the superflycss organization i have different types of projects (Utilities, components, tasks) and each projects is tagged with a corresponding topic. I'd like to provide links that can be clicked on that will display the organization view by a certain topic. For example:
https://github.com/superflycss?topic=utilities
I found one way of doing this that is less work. It allows me to skip adding topics to the project and instead just uses the organizations search field to generate the link. For utilities I just went to:
https://github.com/superflycss
And typed utilities in the Search repositories field, which produces the following URL:
https://github.com/superflycss?utf8=%E2%9C%93&q=utilities&type=&language=
I then use this within other areas to reference the utility projects within the superflycss organization:
utilities
Related
I'm currently inside an organisation in GitHub, which is divided into several teams. I have previously used the GitHub search bar to search for specific text inside a repository, and after starting to use GitHub Enterprise I also started searching by organisation as well.
However, in some scenarios I don't want to search inside the whole organisation, but only inside content owned by a particular team. I tried the syntax below:
org:<ORG> team:<TEAM> <text to search>
Which isn't referenced in any docs that I looked so far, but I got the result below:
Which make me think that is actually possible to do some searching based on a team, since the error was about the team's name, and not about the search syntax.
So, is there a way to search based on a team? If so, how should I do it?
In order to search with the team: or team-review-requested: filters you need to use the team's full name, which would be in the format of <org>/<team>, see GitHub's docs on using search to filter issues and pull requests. In your example, the following query should work:
org:<ORG> team:<ORG>/<TEAM> <text to search>
When creating a new feed in a private project there is the option to choose visibility between the whole related Azure Active Directory, the whole org and specific people.
In the official docs about project-scoped feeds it says:
With the introduction of public feeds, we also introduced project-scoped feeds, which live inside the project that they were created in, and can only be seen when accessing the Azure Artifacts hub within that project.
How is that sentence to be understood compared to choosing the visibility (during feed creation) to be e.g. the whole organisation?
To me this sounds like although the feed is project-scoped it still can be read-accessed by any person within the organisation.
Can you help with my understanding?
With the introduction of public feeds, we also introduced
project-scoped feeds, which live inside the project that they were
created in, and can only be seen when accessing the Azure Artifacts
hub within that project.
It means if we create a project-scoped feed FeedA in project ProjectA, we can't see details about FeedA when we're in another project. (Even though we're Porject Collection Admin!)
So in ProjectB, we can only see organization feed and project-scoped feeds created in current project. To see UI of FeedA and to manage its settings, we have to navigate to project ProjectA.
How is that sentence to be understood compared to choosing the
visibility (during feed creation) to be e.g. the whole organisation?
The visibility during creation here actually represents the permissions about Views.
When you choose visibility Members of current organization:
When you choose visibility Specific people:
Now just like the document says, to see the details about the feed we have to navigate to the project where the feed is created. Let me share an example for better understanding:
1.I'm member of ProjectC with project reader role:
2.In ProjectC I created feed FeedC with visibility: Any members in current organization
3.Now I'm the member of current project=> I can see the FeedC in ProjectC. Also the View permissions are FeedUser+MemberInOrganization, so I can see the packages in FeedC with #Local View.
4.Edit the view to make the view's visibility to be Specific people:
5.I'm the member of current project=>I can see/access the FeedC=>But I can't see packages with #Local view in FeedC any more. That's it!
Summary:
Project-scoped feed determines that we can't see the feed in another project. (We must navigate to one project to see the Feed in UI page.) Visibility determines that even when I'm member of that project, I can't see part of the packages if the view permissions is set specific people.
Ps: ProjectSamples is the name of my test organization...
Or developers need the Work Item forms as designed for our agile process, but we'd like our regular users to be able to add new bugs and user stories using a simplified form, where a lot of fields are removed and some have team specific default values.
How can this be done?
The closest match I've found so far is templates, where field defaults can be defined, but the form that's used/displayed is still the large cluttered one. Being able to use the template link to land directly on a pre-filled form is a step in the right direction, though.
Azure DevOps allows you to modify your process template and add new work items to your project. You can find the documentation to do this here.
Go to Organization settings for your account --> Process --> Create an inherited process from your process template --> New Work Item Type.
You can then define the fields you want and the layout of the template.
Something else that could be useful in your scenario is the Test and Feedback Extension. This is a simple browser plugin that lets users explore feedback requests and file comments and bugs.
I'm looking to create a nice dashboard in VSTS with a set of relevant charts for my collegues so they can keep track of things.
We have a project for keeping track of it operations tasks. In this project we've created different Features for different departments of the company.
Is there a way to filter the user stories by parent/feature so that I can make different charts for different departments? I've managed to create a "Work items and direct links" query that actually only outputs the User stories in one feature, but such queries can not be used in charts unfortunately.
Other workarounds would be acceptable too.
There is a Work Item Visualization extension that you can check whether it meets your requirement (Can highlight specified work items).
Another way is that you can custom a dashboard widget or other extension to display the result: Add a dashboard widget.
There are many extension samples that may benefit you: vsts-extension-samples
I currently have a few projects pages and I’m looking to display a list of team members that are associated with each project (a member may be associated with multiple projects) but I’m not sure how I can create this. A taxonomy doesn’t provide enough information (ideally want to show an image with name and short bio) so I’m assuming I’ll need to create a /team-members/ page with member pages below it and pull this in somehow to each project.
How would I go about allowing team members to be added to projects through the admin panel?
Basically you can create a page for each team member. These page can be unvisible if you don't want to display them alone
Then you create one page for each project.
When you want to use one member page as a part of one project page, you just include it:
{{ page.find('/some/other.page').content }}
Note that the above code may require you to activate twig parsing on your pages.
This way you can include the same team member in several project pages and update team member content in only one place from the admin panel.
Another approach is to create a plugin that will enable you to manage projects and member as you want to, but it may be a little overkill given Grav can do what you want out of the box.