How can I record custom attribute logs on GitHub issues? - github

I have added some custom attributes to my project on GitHub. This project is shared, and I want to record any changes to these attributes. How can I do that?
I have no opinion about this subject

Related

Who can access / see project-scoped feeds?

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...

How do I load PRs from multiple repos from a SearchIssuesResult? The items have no repository IDs

I'm trying to find all PRs across all repos that have a given branch name. I'm using GitHub Enterprise.
SearchIssuesResult contains a List<Issue> Items property. The individual Issues in that list have a Repository property, but it is null, and its sibling property PullRequest doesn't seem to have all the data populated in it.
I therefore want to load the PR directly using the PullRequestsClient.Get method or similar, but this needs a repository ID. I've hit this with a debugger and the Issue results don't seem to contain one anywhere in the hierarchy.
I can infer an owner and name from various URLs that I do have available (e.g. the HtmlUrl property on the Issue) but that seems very hacky and ugly. Is there a better way to do this than relying on URL formats?

Trigger a plugin step on "entityimage" change

I created a plugin that should upload the contact entity "entityimage" to an external storage.
The code itself should works (it works as a console app), but I am unable to add a step that trigger on "entityimage" change as I can't find it in the filtering attribute list in the Plugin Registration Tool.
Is there a way to trigger this plugin only when "entityimage" change?
Regards,
Dremor
Reviewing the Contact's entityimage field in the Metadata Browser indicates that it is a "Virtual" field, which may be why it is unavailable as a filtering attribute.
Also, according to the SDK there does not appear to be any other message available besides "Update" on the Contact that could be used to indicate that the entityimage has changed.
And, changing the image through the UI does create an Audit History entry, however, it is a generic "Update" entry, with the old value and new value blank.
It appears that triggering a plugin on change of only the entityimage field is not possible, nor do there appear to be any OOB hooks to see if that field has changed.
The only other think I can think to research is Change Tracking. Otherwise it looks like you may have to upload the image on any Update of a Contact.
Or, you could sync the image URL's from CRM to an external system and compare the one in CRM to the external system before uploading.
Strangely enough, if you don't set any filtering attributes the plugin does get triggerd when changing the image, but i guess this also means that all field changes will trigger it.

Filtering a github organization's projects by topics

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

How to handle page relationships in Grav CMS?

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.