GitHub project board not copying with repo; is this possible? - github

I've set up a public GH project board that I wanted to share with some people, but when they fork it, only the code transfers over and their project tab remains empty. How can I share this so people can use it? I tried setting it up as a template but that didn't help.

I never seen the notion of "fork" for a project board. Only link.
See "Linking a repository to a project board"
Anyone with write permissions to a project board can link repositories owned by that organization or user account to the project board.
You can link up to twenty-five repositories to your organization or user-owned project board.
Linking repositories makes it easier to add issues and pull requests from those repositories to your project board using Add cards or from the issue or pull requests sidebar

I don't believe GH can do this. Gitlab can.

Related

IntelliJ & GitHub: How to create an organization-based repository

I am a noob at both GitHub and IntelliJ, please answer in that context and be patient.
GOAL:
I need to create a repository for my IntelliJ project in my organization, not my personal account, and be able to Admin it.
NOTE: I do NOT have admin rights for the organization, but I can create projects on it through the GitHub interface and setup a team for it with Admin rights. So, the goal should be feasible.
PROBLEM:
I am using IntelliJ (and its integrated GitHub support, not a separate windows github app install).
When I use the IntelliJ "Share the Project on GitHub" I am not given the option to choose whether to place the repository in the organization, it automatically places it in my account's list of repositories.
Then if in the GitHub website I try to transfer ownership from my account to the organization, it moves it but I lose all Admin rights. I tried to add a team I defined in the organization as collaborators to see if I could grant myself Admin rights through the team before I transfer ownership but the team does not appear.
2nd (related) PROBLEM:
Files committed from IntelliJ show as successful in IntelliJ but do not display in the Code section of the GitHub website. The message in that page mentions creating or uploading a file even though in theory IntelliJ did that.
QUESTION:
Is IntelliJ's GitHub integration usable, especially for organization-based repositories? Or should I install the windows command-line GitHub app and do all of my version control from there?
If the first, is there a good tutorial for creating org-based repositories in IntelliJ?
SOLUTION (I figured it out):
Create the project repository inside the organization.
Click on the repository to open it. Copy the URL.
In IntelliJ create a new project from VCS. Past the URL and hit CLONE.
Add your project contents, commit and push.
Much simpler than I expected... once figured out.

Does Github Project Classic not exist anymore?

In my previous Github repos, I was able to create a project under the repo which was specific to the repo, but now I cannot see this option for the new repos.
I can still use Project (Classic) in my previous repos.
Github now push me to create a project under my account, and link to the repo, but I want to create a project just under the repo.
In my side, the problem is that, when I try to create an "Issue", the user can see all of my projects under my account, but I don't want that.
The user should only see the related project.
Can I somehow have the previous version of the projects?
Thanks

Where to find GitHub project boards I have been added to as collaborator?

I have created a project board on Github and added another user as a collaborator to this private project. He can't find the project under his own project list but only if I give him the direct link.
Double-check the permission granted for that user for the project, using the GitHub API
But I suspect that, unless your project is an organization project (where you can add a collaborator), a collaborator would not see a private project in their own project list unless given a direct link.

Github: Repository > Projects vs Organization/User > Projects

My case is that I'm a member of an organization and I'm assigned to lead a project.
In my Github org, I created a Project corresponding to the project's name and my member initiated a Repository.
Inside the Repository is this:
I'm just a bit confused right now. How do you guys go about this? You have an Org>'Project' where you initially plan to organize your issues etc., and what do you do with this one?
Your organisation can have “projects” just like users, and any repository can also have “projects”. Your organisation project might list the TODOs for your organisation, but for your repository you might have a board to track issues/PRs etc specific to the repository.
Read more:
About Repository Projects
managing organisation projects

what is the difference between github project and project inside repository?

I know this question sounds dumb, but I am unable to understand the difference between the main project and project option provided inside each repository.
Are they same? (But the URL differs)
I looked at help.github.com
but it doesn't help.
I basically understand that for larger projects management, project inside repository is helpful.
on what uses cases, they provided the another project outside of repository and linking those repositories to it?
Is that for structuring?
There is a repository on github (sometimes called a "project") where you store your code. You change the code, make a git commit, and push those code changes to the github repository.
GitHub also has a feature called "projects" which provides you a method for managing the work that needs to be done on the code. GitHub also has "issues", an issue tracker. You can use the GitHub Project Board to organize your GitHub issues, giving you a way to see see where things are at in your effort on the code.
You can turn off the "projects" and "issues" features in the repository settings, you don't have to use them. The center of work is the code in the repository, which might be referred to as a project -- the Projects feature lets you manage your issues in GitHub in a more visual format.
The difference is in the scope. The "main project" (user-owned project board) can have issues and pull requests from multiple repositories whereas the "project in repository" (repository project board) can contain only the issues and pull requests belonging to that repository.
From the Project boards docs:
Types of project boards:
User-owned project boards can contain issues and pull requests from any personal repository.
Organization-wide project boards can contain issues and pull requests from any repository that belongs to an organization. You can link up to twenty-five repositories to your organization or user-owned project board...
Repository project boards are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories.