Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • G git-eca-rest-api
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse FoundationEclipse Foundation
  • IT
  • APIs
  • git-eca-rest-api
  • Issues
  • #84
Closed
Open
Issue created Oct 14, 2022 by Christopher Guindon@cguindonOwner

Non-Eclipse project repository detected: ECA validation will be skipped

This error message is not really useful when trying to debug failures such as the one reported here: eclipsefdn/helpdesk#2081 (comment 1028015)

I do understand that we might not be able to determine what project the fork is for. However, I think we should be able to warn the user of any potential ECA problems.

For example, we should be able to validate if the author has an ECA on file regardless of their committer status and inform the user.

The error in the UI is not really useful, it simply returns 'An error occurred while merging. Try again.'.*

*That's assuming that the error is triggered by the ECA validation. We should be able to determine that once we found the root cause of the issue that was reported.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent