-
Notifications
You must be signed in to change notification settings - Fork 65
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
contrib: add community contrib feature #79
Conversation
等待上游分支合并后再结束 draft 状态。 |
贡献的 PR 可以添加 |
插件化工作还在进行中。下面是一些暂时思考到的一些想法。 贡献子主题/插件的意义:
插件化工作的意义:
|
目前的添加插件的流程:
|
目前考虑到的要review什么:
|
目前能够考虑到的类型:
|
内核还要做什么:
|
85e6de8
to
05a8a94
Compare
This reverts commit f39a811.
This comment has been minimized.
This comment has been minimized.
我觉得创建一个 good first issue 后 改一下yaml 可以合并了 |
成功!晚点一定( |
yaml 多看看 我不知道对不对(push还没试 |
👍 不好意思啊,我前段时间在准备考试,我考完试来看看 |
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.
Rest LGTM, good work!
) | ||
}} | ||
- uses: jungwinter/comment@v1 | ||
if: github.event_name == 'push' |
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.
Do we really need to comment on pushes? I would prefer only doing comments on pull-requests.
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.
The intention here is to make a collection of templates in an issue so that the user could select the theme in an easier way. Since the doc of the plug-in will not be included in the repo. It is a workaround for that.
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.
And it has not been tested.
id: contrib_png | ||
with: | ||
path: ./build/contrib.*.png | ||
client_id: ${{secrets.IMGUR_CLIENT_ID}} |
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.
Everyone who creates PR can now access this secret. Is it expected?
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.
It seems that if someone pulls a request, then collaborator approves it, the secret could be accessed. (idk)
如果 @cascades-sjtu 感兴趣的话,可以发个 issue 用于整合,然后修改 yaml 里的 issue 号,这个分支就可以合并了 |
那我发 issue 准备合并了( |
滋瓷! |
ci 我再修修 试试一些功能后 争取过年后 release( |
建设社区
希望添加一个
good first issue
来提高社区建设:开发者可以向根目录下的contrib
目录添加自定义的模板(子主题)。并添加内置指令\getcontribdir{#1}
获得#1
主题的文件夹目录\getcontribpath{#1}{#2}
获得#1
主题的文件夹#2
文件路径\usemytheme{#1}
使用#1
子主题,在加载sjtubeamer
主要主题后使用\definelogo
添加一个可选参数用于接受文件夹路径这样就可以固化一些社区贡献模板,每一个文件夹就是一个小工作区,可以添加一些自定义图片,环境有了隔离。并且并没有离开 sjtubeamer 的开发环境,可以
sjtucover
和sjtuvi
的所有工具\EqualOption{}{}{}
可以判断其他文件的参数情况,由于\usemytheme
在主要主题入口文件定义,不能在仅加载inner
或outer
主题时使用my主题,也就意味着整个主模板在完整加载的状态。sjtucover
中但是加载参数可以通过内部接口传递。.ltx
文件并不能接受参数,希望添加其他参数应该向内核提供 PR。(或者等我想到了更好地传递参数方法,我觉得可以不允许添加额外的子模板参数,这样可以保证整体的统一性)而 Release 时不会放入这些contrib文件夹,直接下载 Code 会下载这些社区贡献子主题。(这样就更应该下载 Release 了)