Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Please add how to link forked repo to a project board #523

Closed
poovanna886 opened this issue Oct 14, 2020 · 12 comments · Fixed by #3774
Closed

Please add how to link forked repo to a project board #523

poovanna886 opened this issue Oct 14, 2020 · 12 comments · Fixed by #3774
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue

Comments

@poovanna886
Copy link

poovanna886 commented Oct 14, 2020 •
edited
Loading

Add steps to docs.github.com on how to link a forked repo to a project
@welcome
Copy link

welcome bot commented Oct 14, 2020

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 14, 2020
@janiceilene
Copy link
Contributor

👋 @poovanna886 Thanks for opening an issue! Please update this issue using the content issue template to help everyone understand exactly what you're looking for 💛

@poovanna886
Copy link
Author

name: Improve existing docs
about: Add steps on how to link a forked repo to a project board in github.
title: ''
labels:

  • content
    assignees: ''

What article on docs.github.com is affected?

https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-repository-to-a-project-board

What part(s) of the article would you like to see updated?

Adding a forked repo to a project can be of immense help to developers so please add this feature on github

Additional information

@chiedo chiedo added core and removed triage Do not begin working on this issue until triaged by the team labels Jan 13, 2021
@felicitymay felicitymay self-assigned this Jan 15, 2021
@felicitymay
Copy link
Contributor

👋🏻 Hi @poovanna886

Thanks for raising this issue and for adding the extra detail to explain the change that you'd like to see. I'm going to check in with our engineers to find out whether it's possible to add a fork to a project board. It may be disabled because forks often behave differently from other repositories.

@felicitymay
Copy link
Contributor

felicitymay commented Jan 20, 2021 •
edited
Loading

👋🏻 @poovanna886

I talked to the engineers who work on project boards and it seems as if you've uncovered a bug. This is now raised in an internal issue.

Update: One of the engineers later pointed out the fact that you can only add a repository to a project board if issues are enabled for that repository. Forks are created with issues disabled. I hadn't realized this, but it makes sense.

To enable issues on a forked repository:

  1. Go to the forked repo.
  2. Click Settings.
  3. On the Options page, under "Features", check the box next to Issues.

After this, you should find that you can link the repository to your project board in the normal way. I tried this out and it worked for me.

Thank you for reporting this problem, I'll write a content design plan to update the documentation here to help other users of forks. 🙇🏻‍♀️

@felicitymay felicitymay removed their assignment Jan 20, 2021
@janiceilene janiceilene added the fixing internally This will be fixed internally label Jan 20, 2021
@felicitymay
Copy link
Contributor

👋🏻 @poovanna886 🎉

Hi, I have better news. Another engineer on the team asked me to check whether I'd enabled issues for the forked repository, and it turned out that I hadn't. I've updated the comment above with the new information to reduce confusion of anyone else who comes across this issue. You should find that you can link your forked repository to a board if you follow the instructions above first 😄

@felicitymay
Copy link
Contributor

Content design plan

Proposed content design plan to address this issue.

When I looked more closely at Linking a repository to a project board, I realized that it already had a note box at the start of the topic that I had entirely overlooked. While it doesn't mention forked repositories, it does explain that only repositories with issues enabled are available to be added. I think that it would be helpful to reposition the note closer to where you are linking repositories, so that it provides troubleshooting assistance and expand it to mention that issues are disabled by default for forks.

Topics to update:

  • Linking a repository to a project board
    • Move the note box from the start of the topic, to just before the "Further reading" heading, so that it's clearly visible while you are reading step 6.
    • Expand the information in the note to explain that issue are disabled by default on forked repositories.
    • Mention that you can check whether issues are enabled for a repository by checking for an "Issues" tab on the main repository page. (The existing suggestion is only possible for repository administrators and this is a simpler check.)
    • Revise the text: "For information on how to see if issues are disabled for a repository, see" to something more like "For information on how to enable or disable issues for a repository, see"

@felicitymay felicitymay added good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue and removed fixing internally This will be fixed internally labels Jan 22, 2021
@felicitymay felicitymay added the content This issue or pull request belongs to the Docs Content team label Jan 22, 2021
@poovanna886
Copy link
Author

Thank you for looking into it! @felicitymay

@shades-7
Copy link
Contributor

Hey can I work on this?

@felicitymay
Copy link
Contributor

Hi @shades-7 👋🏻

I'm not aware of anyone else working on this, so that would be great.

You may want to check the CONTRIBUTING guide for tips, tricks, and things to be sure you do when submitting PRs to the project.

Thanks for the interest!

@shades-7 shades-7 mentioned this issue Feb 18, 2021
Merged
3 tasks
jnidzwetzki pushed a commit to jnidzwetzki/docs that referenced this issue Oct 6, 2022
@JLockerman @Loquacity
@jacobprall @davidkohn88
Create Function Pipelines How-TO (github#523)
76e0c2c 
* Toolkit How To docs (github#504)

* File setup to rename section and move install doc in

* Add pages for hyperloglog and counter agg from previous PRs

* Add approx percentile blog post link.

* Add new pages to top level page list

* Remove unused entry

* Index & metadata for hyperfunctions.

* Editing metadata

* initcaps in index

* Add new bucket items with filler content.

* Update index and add other required pages

* Add first draft content

* First draft content for remaining dummy text

* Add directory type in index

* Add comment

* Update xrefs in top level pages, add advanced page, edits.

* typos

* Updates per feedback

* Complete edits on counter aggs example

* Add whitespace around procedure tags

* Add function pipeline content with FIXME blog link

* Final editing pass

* Toolkit API docs (github#514)

* add trailing slash (github#505)

* Create 'legend' for API reference tags (github#503)

* write page

* update link name

* typo

* Apply suggestions from code review

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update api-tag-overview.md

Remove 'Edition'

* add line breaks

* Update api/api-tag-overview.md

Co-authored-by: Lana Brindley <github@lanabrindley.com>

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update max storage to 16TB, and some light editing. (github#507)

* Update title of Promscale tutorial (github#512)

* Add approx count distinct functions

* Add counter agg functions

* Procedure styling jacob (github#515)

* update

* add procedure block instructions

* convert styling to procedrue on cloud/disk management

* Apply suggestions from code review

Co-authored-by: Lana Brindley <github@lanabrindley.com>

Co-authored-by: Lana Brindley <github@lanabrindley.com>

* Update xrefs in approx count distincts pages

* Update xrefs in stats agg pages

* Update xrefs in gapfilling pages (+ light editing)

* Update xrefs in percentil approx pages (+ light editing)

* Update xrefs in counter agg pages

* Update xrefs in time-weighted average pages

* Add missing call

* Updates index with new structure, and adds top pages for each family

* Fix typo in index

* Edit index pages

* hyperfunctions intro

* Updated advanced aggs pages with links to HowTo

* Add toolkit matrix table portions to function family pages

* Add links to function family pages

* Add missing link ref

* Fix bad link

* Final editing pass (1 of 2)

* Final editing pass (2 of 2)

Co-authored-by: Jacob Prall <prall.jacob@gmail.com>

* Create function-pipelines.md

* Add how-to function pipelines

Catchall doc for everything the `->` can do.
We'll split it out in a more principled manner later.

* Add function pipelines to the index

* Using .* to produce proper table output in examples

* remove ellipses

* Move pipelines doc into hyperfunctions How To

* Edit about page for new section

* Editing pipelines doc

* Editing pipelines doc

* Add Toolkit & Experimental tags

* Add toolkit_experimental in examples

Add toolkit_experimental schema qualification in a couple examples
that didn't have it already.
A couple other small fixes.

Co-authored-by: Lana Brindley <github@lanabrindley.com>
Co-authored-by: Jacob Prall <prall.jacob@gmail.com>
Co-authored-by: davidkohn88 <35269003+davidkohn88@users.noreply.github.com>
Co-authored-by: Brian Rowe <brian@timescale.com>
Co-authored-by: davidkohn88 <david@timescale.com>
@GitauHarrison
Copy link

👋🏻 @poovanna886

I talked to the engineers who work on project boards and it seems as if you've uncovered a bug. This is now raised in an internal issue.

Update: One of the engineers later pointed out the fact that you can only add a repository to a project board if issues are enabled for that repository. Forks are created with issues disabled. I hadn't realized this, but it makes sense.

To enable issues on a forked repository:

  1. Go to the forked repo.
  2. Click Settings.
  3. On the Options page, under "Features", check the box next to Issues.

After this, you should find that you can link the repository to your project board in the normal way. I tried this out and it worked for me.

Thank you for reporting this problem, I'll write a content design plan to update the documentation here to help other users of forks. 🙇🏻‍♀️

I am trying to link my fork to such a repo (private - I have been added as a collaborator to a repo and the related project board) following this guideline:

  1. On the Options page, under "Features", check the box next to Issues.

After refreshing, I still cannot see the link pop up in my fork.

no_link

The Issues section is checked as recommended.

checked_issues

What could I be missing? I have also followed this article but it is not clear. I intend to see this board live as it is on the main/original repo so I can update it from my fork.

@GitauHarrison GitauHarrison mentioned this issue Dec 27, 2024
Closed
@felicitymay
Copy link
Contributor

@GitauHarrison 👋🏻

This issue is from 2020 and projects have changed a lot since then.

The article that you looked at: Linking a repository to a project (classic) - GitHub Enterprise Server 3.15 Docs is intended for users of GitHub Enterprise Server 3.15 who want to link to a Classic Project.

If you are using GitHub.com, then these instructions are outdated because Classic Projects have been retired on this platform. The new projects work in a different way from the classic projects. The most similar article I can find is: Adding your project to a repository - GitHub Docs. Since it states: "You can only list projects that are owned by the same user or organization that owns the repository." this doesn't seem possible for forked repositories.

I'd recommend asking this question in our community: https://github.com/orgs/community/discussions/categories/projects-and-issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

adding how to link forked repo to a project board shades-7/docs
6 participants
@felicitymay @chiedo @janiceilene @GitauHarrison @poovanna886 @shades-7