.github's People
Forkers
avallecam.github's Issues
Add issue templates available across the epiverse-trace organisation
linelist provides generic issue templates we might want to re-use. They are already re-used in epiparameters.
https://github.com/epiverse-trace/linelist/tree/main/.github/ISSUE_TEMPLATE
https://github.com/epiverse-trace/linelist/tree/main/.github/PULL_REQUEST_TEMPLATE
More visibly call for use case reports
We currently mention it in the CONTRIBUTING guide but only a subset of users will look at it.
We could potentially add a small banner on our documentation website, or add startup messages, to make it more visible.
Add generic contributing guide available across the epiverse-trace organisation
It could be useful to have a generic contributing guide to use as a default for epiverse-trace package that doesn't need / have a more specific contributing guide.
Examples:
Issue in bug report issue template
I believe there is an issue in the bug report issue template which was caused by 81d80ea. The template no longer appears as an option on other Epiverse packages and there is an error message shown when viewing the file on GitHub.
Pull request template will not work by default
GitHub doesn't implement selection of templates for Pull Requests as for Issues so the current template (as long as it's in a subdirectory) will not be used.
Directly include code of conduct
While reviewing this repo, I noticed the code of conduct links out to two Google Docs, which are not tracked in this repository directly.
Might it be an idea to directly include the code of conduct in the repo as a markdown file? I'd be happy to port it over if we want this.
My arguments for moving it over:
- Reduce amounts of clicks needed to access the relevant content
- Version-control of document history (including revisions)
- It will be a great time to also review the contents as they're still denoting Anna and Claudine
Would be interested to hear your thoughts @Bisaloo.
Herdstat workflow failing due to newly protected `main`
The herdstat
workflow is failing because the main
branch recently got protected (I think, cc @Bisaloo). It worked before because main
was unprotected at that time.
I will shortly submit a pull request that updates the workflow to create a pull request to update the contribution graph instead. This helps circumvent the branch protection without having to remove it (because it's there for good reason).
Guide to Epiverse GitHub actions for new contributors
It would be useful to have a guide somewhere for what contributors should do if GitHub actions fail, or what common reasons are (e.g. to point them to when submitting PR). Currently the risk is that we have a barrier to entry for new contributions, given default interface isn’t always that informative (e.g. exit code below).
Highlighting this contributor guide in {EpiNow2} that @jamesmbaazam pointed to – sounds like an opportunity to collate advice.
![render](https://private-user-images.githubusercontent.com/8329046/342368224-21c9058c-ecdb-4727-a47c-3b4a58985f5b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQzNDUzNDYsIm5iZiI6MTcyNDM0NTA0NiwicGF0aCI6Ii84MzI5MDQ2LzM0MjM2ODIyNC0yMWM5MDU4Yy1lY2RiLTQ3MjctYTQ3Yy0zYjRhNTg5ODVmNWIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgyMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MjJUMTY0NDA2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjYxNDQ0NzgyNDM5MzhmN2ViMjQzNjgyOWJkYjFjNmU5ODUzODI0OTYwZGYzNTczZTA2M2Y1MmVjMWExM2M1OCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.2ihivw7H0V742jao3eFr-ZzZGszsqSB_DcxQdKKzCmY)
Code of Conduct revision
I don't know when the code of conduct was last revised, but it appears to be out of date given the committee members are not all part of the project anymore.
This issue is to track the known items that need to be revised, and provides a space to discuss what changes may need to be revised as well.
This issue is to discuss purely technical/logistical details regarding the Code of Conduct, as I presume the substantive content is subject to the committee's decisions.
Revision items
These items will be updated based on the discussion.
- Add latest revision date to document
- Where should input for feedback on the CoC go? Anna's email still mentioned (#34)
Review who has access to the Google Form and where this information goes upon submissionReview Google Form content itself (also mentions committee members no longer present)- Committee membership
- Mentions of "Community Manager" throughout the document may not be relevant anymore as there is no current community manager?
- "You may also make a report directly to one member of the Committee by contacting them directly" - no direct contact information is provided - do we add this? (best practice)
Issue for documentation issue
I think the issue template is missing an entry for documentation issues - which aren't a "bug" as such or a feature request.
update community manager and email
Should we redirect to get in touch with us on the Discussions page?
Lines 1 to 3 in 95a73cc
Exclude RcppExports from linting
This issue is to request that R/RcppExports.R should be excluded from linting as part of the lint-changed-files workflow. The current list aims to exclude unchanged files but also overrides the default exclusion of RcppExports.R, which triggers the line length linter.
I first noticed this issue due to a failing workflow in epiverse-trace/epidemics#135. I missed an earlier instance of this issue in epiverse-trace/epidemics#130 as @bahadzie edited R/RcppExports.R to satisfy the linter, and I ignored the file as it's usually auto-generated.
Consider adding an activity graph to the org README
Could use:
Don’t use ${{ }} syntax in the run section
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.