Skip to content
This repository has been archived by the owner on Sep 1, 2024. It is now read-only.

Migrate Afterglow issues to Alpenglow #27

Open
16 of 45 tasks
egeerardyn opened this issue May 16, 2016 · 2 comments
Open
16 of 45 tasks

Migrate Afterglow issues to Alpenglow #27

egeerardyn opened this issue May 16, 2016 · 2 comments

Comments

@egeerardyn
Copy link
Contributor

egeerardyn commented May 16, 2016

In the Afterglow repository, there are quite a few open issues and PRs.
We should make sure that we incorporate the relevant ones in our repository.

For convenience, I have made a TODO list here with the data from the GitHub API.
Checked items do not need further action (i.e. are migrated already, are not relevant here, ...). For most I have provided a reason.

Already migrated

Issues/PRs that already have their own issue report here.

Status Issue here Reference in Afterglow Description
#17 IR17 and IR17 Light Theme?
#18 PR121 Gitgutter support?
#24 IR127 and IR128 Port to other editors?

Pull Requests

Issue Reports

Note: feel free to edit/update this post when necessary!

@egeerardyn egeerardyn changed the title Tackle issues from Afterglow repository Migrate Afterglow issues to Alpenglow May 17, 2016
@vikjam
Copy link
Contributor

vikjam commented May 19, 2016

I think we're good on PHP and Ruby:

screen shot 2016-05-19 at 2 08 00 am

I think d416f82 fixed PHP. I hadn't noticed any need to do anything about Ruby.

@egeerardyn
Copy link
Contributor Author

I suspect the Ruby issue might be related to the Rails/ERB one that is indeed solved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants