-
Notifications
You must be signed in to change notification settings - Fork 45
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
Build on forks with a static data file #3
Labels
Comments
Ideally #2 is solved first. |
Some sample data can be found at https://github.com/i5o/gcileaderboard/tree/master/orgs/2016 |
Load the data from there, so we do not keep a copy in our repository, as it is not our data. |
Now we have a data model, it is also possible to use https://github.com/gregmuellegger/django-autofixture |
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 10, 2017
When the GCI token is not available, the GCI page should fail to build, while letting other parts of the website be build. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 10, 2017
When the GCI token is not available, the GCI page should fail to build, while letting other parts of the website be build. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 10, 2017
When the GCI token is not available, the GCI page should fail to build, while letting other parts of the website be build. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 10, 2017
When the GCI token is not available, the GCI page should fail to build, while letting other parts of the website be build. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 11, 2017
The public/ rendered version contains the word coala, and thus needs to be ignored from the KeywordBear rule. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 14, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 14, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
Merged
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 14, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 14, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 16, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 16, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Separates the fetch operation from the load operation, allowing the build on forks to use a cached dataset. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
Before the Google Code-in data can be stored in the repository, the data of students who are just starting needs to be removed, the status types need to be simplified to reduce side channels, the unpublished tasks need to be removed, and task mentor list needs to be removed. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
The cleansed data can be fetched from the production website if the origin remote is set to be production repository, as it is on pull requests for Travis CI. This does not yet allow branch builds on forks, as their origin will not be the production repository. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
The GCI exported data contains 'coala', so it needs to be excluded from the relevant checks. Also ignore private/** and delete it regularly, as a preventative measure for accidental leaks. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
The GCI exported data contains 'coala', so it needs to be excluded from the relevant checks. Also ignore private/** and delete it regularly, as a preventative measure for accidental leaks. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
The command had missing imports and incorrectly used yaml. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
The command had missing imports and incorrectly used yaml. Related to coala#3
jayvdb
added a commit
to jayvdb/community
that referenced
this issue
Dec 17, 2017
In Travis CI Pull Requests, the GCI data has been loaded from the previous production build, but the GitHub and GitLab tokens are not available, preventing any students from being linked to GitHub or GitLab, resulting in an empty list. Related to coala#3
hey i want to work on this issue |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can export a subset of the data as yaml/json, and store it in the repository, so that people can develop without access to a GCI API token
The text was updated successfully, but these errors were encountered: