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.

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

Expand awesome issue templates to other publiclab repositories #7141

Open
Uzay-G opened this issue Jan 7, 2020 · 9 comments
Open

Expand awesome issue templates to other publiclab repositories #7141

Uzay-G opened this issue Jan 7, 2020 · 9 comments
Assignees
Labels
feature explains that the issue is to add a new feature

Comments

@Uzay-G
Copy link
Member

Uzay-G commented Jan 7, 2020

In plots2, we have an amazing set of github issue templates for bug reports, ftos and feature requests. I think we should export these to other repositories, like mapknitter, image-sequencer, spectral-workbench and all the others where it would be useful. That way there would be more first timer issues on other repositories and this would simplify things for contributors.

Currently, there are templates in some other repositories. The problem is that they are not used because they are not suggested to contributors when they make an issue. unlike inside plots2. These repos use the old model for creating templates in Github and not the new one.

I am working on implementing this for Mapknitter but would love your help on accomplishing this on the other repositories!
Do you think this is a good idea? @publiclab/community-reps
I'd love to implement the changes! 👍

@Uzay-G Uzay-G added the feature explains that the issue is to add a new feature label Jan 7, 2020
@jywarren
Copy link
Member

jywarren commented Jan 7, 2020 via email

@Uzay-G
Copy link
Member Author

Uzay-G commented Jan 8, 2020

I opened a pull request to begin this on image-sequencer.

@sashadev-sky
Copy link
Member

@jywarren @Uzay-G i think what would be really awesome is if we could look into the option to open a PL repository containing just reusable template files that will pull into every repo. It will make things a lot easier. For ex., if we have a code of conduct change we just update the 1 file instead of 10 or so times across the organization’s repos.

I think Github provides documentation on doing this (sorry for not linking to it - on my phone).

Maybe I can create a GCI task especially for doing this? @jywarren Can be yours if I do @Uzay-G

@sashadev-sky sashadev-sky self-assigned this Jan 8, 2020
@Uzay-G
Copy link
Member Author

Uzay-G commented Jan 8, 2020

I'll look into this @sashadev-sky! Nice catch. 👍

@Uzay-G
Copy link
Member Author

Uzay-G commented Jan 8, 2020

Hey! I figured out how to do what @sashadev-sky suggested using https://help.github.com/en/enterprise/2.17/user/github/building-a-strong-community/adding-support-resources-to-your-project. I made a repository with the default files we can use. Someone with permissions for Publiclab just needs to clone my repo through the organization and it should work.

I could also make/add a default SUPPORT.md file if that would be useful 👍

@SidharthBansal
Copy link
Member

There are multiple PRs here. May I know how many points you expect for each pr?
Which task I should upload?
If there are stale pr then kindly close them

@SidharthBansal
Copy link
Member

I think 2 points for 2 prs. Please do similar changes to other repos too. We will give you points for this plots2/7141 at once

@Uzay-G Uzay-G mentioned this issue Jan 31, 2020
21 tasks
@Uzay-G
Copy link
Member Author

Uzay-G commented Jun 11, 2020

This repo has all the templates. If the publiclab org clones it, then those templates will be expanded to every single PL repo. Could we do this?

@Uzay-G
Copy link
Member Author

Uzay-G commented Jun 11, 2020

@jywarren @Uzay-G i think what would be really awesome is if we could look into the option to open a PL repository containing just reusable template files that will pull into every repo. It will make things a lot easier. For ex., if we have a code of conduct change we just update the 1 file instead of 10 or so times across the organization’s repos.

I think Github provides documentation on doing this (sorry for not linking to it - on my phone).

Maybe I can create a GCI task especially for doing this? @jywarren Can be yours if I do @Uzay-G

If we do it the way I mentioned above, we will only need to changes the templates in one place.

@stale stale bot added the stale label Oct 7, 2020
@publiclab publiclab deleted a comment from stale bot Oct 8, 2020
@stale stale bot removed the stale label Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature explains that the issue is to add a new feature
Projects
None yet
Development

No branches or pull requests

4 participants