Comments (12)
Can you maybe document your workaround somewhere. I actually would like to have it in the README aswell for others who have the same problem
from node-gitlab-2-github.
Oh, this is in the github api module (routes.json) so it's not really something this tool messes with. Please feel free to close this. I'm going to leave it open in case you want to track this.
from node-gitlab-2-github.
If you have created a Issue over at the other repo I'd like to close this issue as I like clean repos.
from node-gitlab-2-github.
I haven't created an issue over there, as I've found a work-around. No reason to keep this one open.
from node-gitlab-2-github.
I'm having this issue too, the Gitlab attachments are linking to https://github.com/uploads/{{GitlabHash}}
instead of either being reuploaded to Github, or remaining linked to Gitlab.
from node-gitlab-2-github.
I think we are currently not migrating any attachments. this commit did add labels to the issues which need attachments migrated manually: 3fd53c8#diff-168726dbe96b3ce427e7fedce31bb0bcR312
A PR migrating that would be awesome !!!
from node-gitlab-2-github.
Yeah, I saw that it adds a label, which is helpful. I think I'll take a look at how difficult it would be to add automatic migrations while my team does the manual one. 😄
from node-gitlab-2-github.
@spruce I don't think labeling the issue with "attachment" is nice.
For my needs, I removed that part and fixed the link to the uploaded files as follows:
in function addMigrationLine(str, item)
if (str.indexOf('/uploads/') > -1)
{
str = str.slice(0,str.indexOf('/uploads/')) + settings.gitlab.url + "/" + settings.github.owner + "/" + settings.github.repo +
str.slice(str.indexOf('/uploads/'))
}
from node-gitlab-2-github.
Ok, But doesn't mean that you need to push all your uploads into you repo? In my understanding the URL gets reformatted to :github.com/owner/repo/uploads/*
, no?
from node-gitlab-2-github.
Actually, not. No need to push the uploaded file to GitHub.
The URL gets reformatted to
GitlabHost/owner/repo/uploads/*
For example, this issue with an uploaded file was merged to GitHub using your code:
Not that the text in GitLab
is a link to the original GitLab-issue.
(just in case something goes south we can still see the original version).^^
Another example with a figure is JuPedSim/jpsfire#9
from node-gitlab-2-github.
But this would mean there now exists a dependency of the new repo onto the old repo. Which I find kind of bad as this destroys the possibilty to move away and shut down your own instance / or beeing locked out later (leaving uni or something similar)
from node-gitlab-2-github.
You make a good point. The perfect solution would be to automatically upload the files to GitHub with some API-commands. Any idea how to to it? From the official GitHub documentation there is no hint about this possibility. (probably it's not possible).
However, I think this issue was about fixing broken links, right?
If someone could figure out how to upload these files to GitHub, then links can be updated easily.
Till then, I don't see a better solution than linking to the old uploads..
(ignoring the files is not a solution)
from node-gitlab-2-github.
Related Issues (20)
- time needed for transfer of issues HOT 1
- Error with `npm i` on Ubuntu 18.04 HOT 2
- some pulls/issues are not migrated on resume
- Migrate merge requests with deleted branches
- Not able to find issues in Github even after migration successful HOT 2
- 'settings' only refers to a type, but is being used as a value
- Label and issues not migrate
- Filter gitlab objects with functions
- Getting a 403 on write to github HOT 1
- You have to enter your GitLab private token in the settings.js file.
- The 'master' branch exists on GitLab but has not been migrated to GitHub
- Feature request: setup repository mirroring from GitLab to GitHub
- Creating issue fails if assigned and mapped user has no write access to repo HOT 1
- Migration of releases fails if release body is null
- "Abuse detected" slowdowns and possible solution HOT 2
- Could not download attachment
- Migrating multiple gitlab repos to Github HOT 2
- VCS migration
- ERROR: "remote: fatal: fsck error in packed object" when pusing to github HOT 1
- RequestError [HttpError]: request to https://api.github.com/repos/{owner}/{repo} failed, reason: connect ETIMEDOUT
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.
from node-gitlab-2-github.