-
Notifications
You must be signed in to change notification settings - Fork 155
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
[#2161] One-Stop Config File for Code Portfolio #2172
Changes from 1 commit
2db2ac0
202d247
f64f6ed
356299a
ffd4912
2cbb662
9190fb0
b611f29
6573637
6c5e401
4259db3
43f1c14
d5fd31a
6e58493
7924629
cbf622d
fa95f75
4299ff2
1145f8e
7c94fea
6ee3249
48c873b
50f6ec6
941f420
6dd383b
d628e85
68ea84e
28d9c84
83329cf
f70ead4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
repoUrl: github.com/user/repo | ||
reportTitle: RepoSense Report | ||
authorDisplayName: Sample Author | ||
authorGithubId: Sample Author Github ID | ||
branches: | ||
- name: Branch 1 | ||
blurb: Blurb 1 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Blurb should allow a few paragraph of markdown text. So, yml might not be the right format for this config file. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
- name: Branch 2 | ||
blurb: Blurb 2 | ||
startDate: 2020-01-01 | ||
endDate: 9999-12-31 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See #2161 (comment) for an example that seems intuitive from the user POV There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @damithc Just wanted to clarify, do you mean that we should include the configs within the markdown files itself, and have the backend parse the markdown files and then generate the reports, or that the overall order/style/keys in the YAML file should match what was used in the example provided? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @asdfghjkxd I wasn't specifically using markdown either. It is just a custom format that makes sense from the user's point of view. I'm fine if something close can be achieved by YAML or some other commonly-used format, provided it makes sense from the user (i.e., the user shouldn't have to do a lot of extra work just to conform to the file format) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @damithc I see, sure thing, we will try to design a user-friendly and convenient config file format and update this PR and parent issue with any new findings/improvements! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@damithc Sure thing, will remove these from the YAML file and other associated classes in a future commit.